Michael Goulet
Michael Goulet
> It's just syntax sugar, it does not affect the language itself Extending the type system to allow function signatures to infer their return types is *not* syntax sugar. It...
This is a rustfmt bug, so it should be opened against the rustfmt repo
> I think you should use IntoFuture instead of `Future` here, since it will allow passing more functions as `impl async Fn(..) -> ..` Yeah, sure, that's definitely possible from...
> `const Fn` could be listed under future possibilities if there is anything from the type syntax interaction that could be used there. I don't really think mention `const` as...
> It's an ad-hoc special case, doesn't fit with some wider language feature, and might even conflict with a hypothetical future effects/keyword generics feature If we did introduce an `async`...
> What about libraries already using FnOnce? Does this work? [Neither](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=5faa5341f6b18631da665fe5154fa751) works currently. I don't particularly think it matters tho -- you also can't intermix `Fn` + `AsyncFn` anyways, so...
> First, I personally am very skeptical that having a separate set of traits for async functions is not the right choice in the long-term (because ideally we do better...
r=me after ci passes, unless you want a review from lcnr specifically
@WaffleLapkin: Yes, it's just pending documentation https://github.com/rust-lang/rust/issues/101336#issuecomment-1251216579 -- presumably this is (A.) on Niko's list.