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
At the moment, some workarounds and shortcuts such as block_in_place and spawn_blocking are used to allow calling blocking functions in asynchronous contexts and simplify the implementation of async counterpart functions. This may not be optimal.
Two things to address with this issue:
Should sync functions with async counterparts be callable in async contexts?
Should async function counterparts be fully implemented?
Whatever is decided, it should be consistent across the whole crate. This isn't really a high priority, but should still be kept in mind.
The text was updated successfully, but these errors were encountered:
At the moment, some workarounds and shortcuts such as
block_in_place
andspawn_blocking
are used to allow calling blocking functions in asynchronous contexts and simplify the implementation of async counterpart functions. This may not be optimal.Two things to address with this issue:
Whatever is decided, it should be consistent across the whole crate. This isn't really a high priority, but should still be kept in mind.
The text was updated successfully, but these errors were encountered: