Ibraheem Ahmed

I would be open to adding this feature but it's not really a high priority for me. It might be easier to put some time into writing a param parser...

Can this be merged?

@seanmonstar can this be merged?

C# lints when there are no `await`s in an `async` function.

- [ ] [Building a shared vision for Async Rust- HN Discussion](https://news.ycombinator.com/item?id=26503809)

- [ ] [Debugging async generator errors in Rust](https://meltware.com/2020/10/21/rust-async-nonsense.html) > My colleague Matt Jibson and I recently found ourselves in the unfortunate situation of debugging this hefty async/await-related error from...

[This was heavily discussed on Hacker News yesterday as well.](https://news.ycombinator.com/item?id=26509505)

There have been proposals for a `global_executor` in the past: - https://without.boats/blog/global-executors/ - https://internals.rust-lang.org/t/global-executors/11295 There has also been discussion about an extension to `Context` that would allow futures to interact...

There are a couple duplicate issues, would accept a PR.

This could mention the [`atomic-maybe-uninit`]( https://github.com/taiki-e/atomic-memcpy) crate in the alternatives section (cc @taiki-e).