Robert Usher

`?` appears to be working fine, however something is tripping up on the `Box` in the `Result` (possibly rustc can't infer the type we actually want somewhere). The following reproduction...

@myyrakle I still intend to fix this properly, but a temporary workaround might be to explicitly cast your boxed error to `Box`. This change applied to my example above looks...

Hmm - I don't have any experience with `no_std`, but at the moment the macro modifies the return type of async functions to something like: `core::pin::Pin` so it'll use whatever...

That unfortunately doesn't work on `std` - for example: ```rust pub struct Wrapper(core::pin::Pin); ``` gives the error: ``` error[E0433]: failed to resolve: use of undeclared crate or module `alloc` -->...

This seems reasonable to me - I've put up #17 to add usage documentation on the macro function.

It _should_ be possible, but this crate was implemented before async fn in traits were stabilized. I'll do some investigations, but in the mean time https://github.com/dtolnay/async-trait (which boxes async trait...