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
I'm fond of node.js's strategy for sync and async APIs. They maintain two copies of a function: one that is sync and one that is not (async). I have not seen this pattern in Rust, but I'm sure it could be ported.
This allows a user to not worry about futures, runtime or "wait"ing. A lot of times, you just want to block, especially for simpler apps.
The text was updated successfully, but these errors were encountered:
I'm fond of node.js's strategy for sync and async APIs. They maintain two copies of a function: one that is sync and one that is not (async). I have not seen this pattern in Rust, but I'm sure it could be ported.
This allows a user to not worry about futures, runtime or "wait"ing. A lot of times, you just want to block, especially for simpler apps.
The text was updated successfully, but these errors were encountered: