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
Right now missionary works on the JVM and in JS. Given a custom ideal runtime
what features would help make missionary simpler/better?
what features would become obsolete or moved into the runtime directly?
I e.g. remember hearing multi-shot continuations would help in some way? I'm wondering which parts of the API are constrained by the current runtimes, which parts of the API are band-aids over missing runtime capabilities etc.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Right now missionary works on the JVM and in JS. Given a custom ideal runtime
I e.g. remember hearing multi-shot continuations would help in some way? I'm wondering which parts of the API are constrained by the current runtimes, which parts of the API are band-aids over missing runtime capabilities etc.
Beta Was this translation helpful? Give feedback.
All reactions