You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's better to have a code action that toggles a function or trait method between async fn method() -> Ret and fn method() -> impl Future<Output = Ret>. Conversion from async fn to impl Future should be lossless, but, of course, the opposite is not.
It's better to have a code action that toggles a function or trait method between
async fn method() -> Ret
andfn method() -> impl Future<Output = Ret>
. Conversion fromasync fn
toimpl Future
should be lossless, but, of course, the opposite is not.It's convenient in cases like:
-> impl Future
function toasync fn
especially it was generated (e.g. When generating implementation for a trait, emitasync fn
for functions that returnimpl Future (+ Send)
#16195)Send
bound to an existingasync fn
to assert the implementation is Send.The text was updated successfully, but these errors were encountered: