Michal Hornický

@SimonSapin You raise an important point. But, like closures, the arguments are available from the start of the generator, since generator is created `suspended` at the start, like closures, and...

Well, the argument HAS to be a tuple, and it HAS to be unpacked inside the argument list of the generator, since it is the behavior of closures, and deviating...

@SimonSapin Yes, this zealotry for theoretical purity has drawbacks. But I believe this is the right choice in this case. The connection to `FnOnce` provides a way we could extend...

I meant the interaction between `Fn*` traits, and how are closures invoked. There have to be some mechanics for packing/unpacking the arguments passed into the closure. // Edit: i meant...

@CAD97 Thank you, I'd be thrilled if you explained how could the type checking work, since i'm not that qualified in this area. I'm going to reformat the RFC in...

Edit: Added an alternative design found on rust forums, please re-read the RFC. For multiple different yield poins you'd have to add multiple lifetime arguments, so I don't think this...

Commenting a way of approaching this. Each view has a `focusable` attribute, which determines whether it can individually hold focus. Primitive edit views like `TextInput` have set this to `true`,...

I encountered similar problem, and started working on temporary solution using feature flags and multiple Runtime implementations. You can see the work here : https://github.com/semtexzv/actix/commit/5dd634bf0eaf2b3e59ffd3cddd8329ce94f7f7ac My goal is to use...