It's too late to remove async fn, but can we still implement his "What if the alternative was nicer"? Is there any good reason why I can't use await in a non-async function that returns a Future?
What I really want is for my synchronous and asynchronous code to be a lot more transparent and not force my hand depending on whether I'm calling from a synchronous or asynchronous context. I know this is a really difficult ask because of the lack of knowledge of what runtime to use when calling an async task in the context of a synchronous call...
Its the coloring problem I ultimately hate fighting against. There are definitely times that I care about it, long running blocking synchronous calls and getting a handle on a Future are really the only ones I can think of and they tend to be the exception not the norm.
I think that "Ability to forgo naming an associated type name." seems very reasonable to me
> Is there any good reason why I can't use await in a non-async function that returns a Future?
You can do this afaik