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
Coroutines and closures have quite similar type structures. It makes sense to provide similar APIs for coroutines as those that exist for closures, like:
Context::closure_sig
Context::resolve_closure
Coverage in Context::fn_sig
The text was updated successfully, but these errors were encountered:
I don't know if we'll be able to promise that we'll be able to refactor all of these APIs in the background without breaking the SMIR API. They change really rarely, so maybe that's not an issue
I don't know if we'll be able to promise that we'll be able to refactor all of these APIs in the background without breaking the SMIR API.
True. Before anything, it's "stable" MIR.
They change really rarely, so maybe that's not an issue
Yeah. Also, we currently have CoroutineDef, and some APIs for it like getting the signature seem to be quite static, even if the background changes in Context.
Coroutines and closures have quite similar type structures. It makes sense to provide similar APIs for coroutines as those that exist for closures, like:
Context::closure_sig
Context::resolve_closure
Context::fn_sig
The text was updated successfully, but these errors were encountered: