Russell Johnston

One thing to keep in mind is that the generator argument used by `async` will be a reference- this means it has none of problems of drop order or generator...

On another note, I think it is *much* more important for generators to unify with Rust's various "effects," than it is to unify with closures. First, like SimonSapin mentions, we...

The "`yield` evaluates to the `resume` argument" approach doesn't have any of those problems. And it doesn't have them precisely because it matches the behavior of normal Rust code more...

I like the idea of `clone ||`, I run into this quite a bit. For reference, C++-style explicit lambda captures were considered pre-1.0. IIRC the reason for what we have...

A minor note on the question of the separator: Using `::` there not only aligns well with existing Rust syntax generally, but I think also aligns well with with 2018...

The downsides of future-possibility [Split the discriminant from the payload](https://github.com/rust-lang/rfcs/blob/c34989cc81c0dbd96ca65a50fe987ad09f5a6251/text/0000-placement-by-return.md#split-the-discriminant-from-the-payload) can be mitigated by applying that split only at function boundaries. Rust already has two separate ideas of how values...

> Can you elaborate? > > In particular, how do you think the following code should be handled, layout-wise? > > ```rust > fn bar() -> Result { > let...

Another possibility might be to make it the backend's problem, but also make sure it is always possible to implement using trampolines as a fallback- that might be acceptable if...

The difference is that you can currently expect to get the latest versions compatible with what *you* wrote in `Cargo.toml` when running `cargo update`. With MSRV-dependent resolution, you might start...

Also related: https://docs.microsoft.com/en-us/windows/uwp/xaml-platform/xaml-host-controls You can now (on new enough versions of Windows) use some amount of UWP UI outside of an appcontainer.