gdxhyrd

25 ms·

1. 121.▲
   by gdxhyrd 7y ago

   Rust futures are just types that implement an interface providing a method to advance execution if possible and signal when they have more work to do.
2. 122.▲
   by gdxhyrd 7y ago

   Rust cannot guarantee the lack of deadlocks or overall thread-safety. It does guarantee no data races, though.
3. 123.▲
   by gdxhyrd 7y ago

   You are mixing up asynchronous IO with non-blocking IO with async syntax sugar. As the name implies, async syntax sugar is a convenience, it does not magically improve performance.
4. 124.▲
   by gdxhyrd 7y ago

   If you are deadlocking, you have a bug. If you hit OOM, you most likely have leaks or went wild with threads or allocations. Both of those conditions are orthogonal to async/thread pools, so what do you mean?
5. 125.▲
   by gdxhyrd 7y ago

   The same can be achieved easily with non-blocking IO with an event loop. In addition, several threads will go faster than one as soon as any two remotes overlap.
6. 126.▲
   by gdxhyrd 7y ago

   That already happens with any competent scheduler, no?
7. 127.▲
   by gdxhyrd 7y ago

   Abandoned? Every single Windows application uses it, regardless of the language, framework or anything else. It is the equivalent to Linux syscalls, since it is the lowest stable layer in Windows land.