3 ms·
> at which point I bet it would be a somewhat easy modification to what Rust has already implemented. You'd lose that bet: https://gankra.github.io/blah/linea
by steveklabnik 6y ago
> at which point I bet it would be a somewhat easy modification to what Rust has already implemented.
You'd lose that bet: https://gankra.github.io/blah/linear-rust/ https://gankra.github.io/blah/linear-rust/
- saurik 6y agoThis is an article about why linear types are hard to implement... and it doesn't even claim they can't be done; regardless, I have argued this at you before :(. https://news.ycombinator.com/item?id=23579426 https://news.ycombinator.com/item?id=23579426 I continue to believe that the strongest point in that article is actually the third footnote, which correctly admits that this is mostly about a lack of appreciation. > The Swift devs have basically the exact same argument for move-only code, and their implicit Copy bound. Hooray! My claim here is that, given linear types, it should be trivial to use async/await style coroutines for I/O continuation. You have given no evidence against this idea.
- steveklabnik 6y agoAh! I misunderstood you, sorry. I thought you were saying that linear types would be easy to implement. I wasn't trying to say anything about the stuff you'd do with them if you had them.