3 ms·
Wohoo. I was waiting for this. I hope that at a later point this will also mean that we get some sort of syntax support for it once it's stable and entered std.
by the_mitsuhiko 10y ago
Wohoo. I was waiting for this. I hope that at a later point this will also mean that we get some sort of syntax support for it once it's stable and entered std.
- kibwen 10y agoWhat sort of syntax support do you have in mind? (Personally I think any language-level support is unlikely, given that Rust doesn't make a point of privileging any particular approach to concurrency.)
- pcwalton 10y ago> Personally I think any language-level support is unlikely I don't. :) Futures are a very generic abstraction that doesn't really favor any approach any more than, say, iterators do.
- the_mitsuhiko 10y agoSee Python 3.5, ES6 and C# and their await stuff. They generally use a form of future internally to abstract this.
- kibwen 10y agoAh yes, I wasn't thinking of async/await. I suppose there's enough precedence from other languages to warrant that, though this is probably far-future work (I don't even expect futures to land in the stdlib for quite a while, though I would like them to eventually).