Nemo157

~~Hmmm, actually #2467 won't fix it since that still relies on reading the `Cargo.toml` to pull the minimum data required to add the crate into the database.~~

See #106, there are compatibility issues with new nightlies because of the [builtin `async`/`await` support](https://github.com/rust-lang/rust/issues/50547).

Could also be related to https://github.com/rust-lang/docs.rs/issues/238, in that if we start generating documentation for examples then they'll have `[src]` links in them.

Everything except the topbar of the documentation pages is generated by rustdoc, we don't really want to be trying to inject extra stuff into the side-bar after the page was...

It seems pinning back to `compiletest_rs` `v0.3.7` instead of allowing use of `v0.3.8` avoids this issue for some reason.

[Comparing the changes](https://github.com/laumann/compiletest-rs/compare/v0.3.7...v0.3.8), I have no idea why these two versions would behave differently. I think this is actually a symptom of a deficiency in Cargo (`compiletest_rs` probably needs to...

One additional step that could be taken with this syntax is to have the body behaving something like the proposed ["throwing functions"](https://internals.rust-lang.org/t/pre-rfc-throwing-functions/5419). That would give a full rewrite of the...

I've just pushed a branch implementing the first part of this for comparison purposes; including supporting returning both `impl Future` and `impl Stream` using a single macro: https://github.com/Nemo157/futures-await/tree/alternate-signatures It does...

@rushmorem my second post there is really a potential extension that I'm not all that confident of either. I don't think it would actually be implementable via macro today (`do...

I've re-added boxed futures/streams by assuming any non-`impl Trait` return type must be a `Box`. It seems like there must be a better way to detect it but I wasn't...