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
{{ message }}
This repository was archived by the owner on Dec 27, 2018. It is now read-only.
Ideally the API should support both sync and async workflows, but that may prove to be too complicated for a single API. Should there be separate sync and async interfaces?
If we use generics over something that determines whether the implementation is asynchronous, then we have to make Ingot generic and not Ingot::handle(), otherwise we prevent making instances into trait objects.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Ideally the API should support both sync and async workflows, but that may prove to be too complicated for a single API. Should there be separate sync and async interfaces?
If we use generics over something that determines whether the implementation is asynchronous, then we have to make
Ingot
generic and notIngot::handle()
, otherwise we prevent making instances into trait objects.The text was updated successfully, but these errors were encountered: