4 ms·
Okay, but this seems like letting the perfect get in the way of the good? A maintained, readable, informal spec should be quite useful as a starting point for w
by skybrian 8y ago
Okay, but this seems like letting the perfect get in the way of the good? A maintained, readable, informal spec should be quite useful as a starting point for writing a more formal spec later.
It need not be definitive. It would be quite reasonable to point out areas that aren't nailed down yet - this is also useful for the reader.
- steveklabnik 8y agoThat's what the reference is, and it's there for exactly that purpose.
- TheCoelacanth 8y agoWhat do you want out of an informal spec that isn't provided by "The Rust Reference"[1]? [1] https://doc.rust-lang.org/reference/index.html https://doc.rust-lang.org/reference/index.html
- edflsafoiewq 8y agoBorrow checking rules.
- cogman10 8y agoI don't know what the current state of affairs is, but this is something they have rightly delayed specing. The original borrow checking rules were quite byzantine compared to what we have today. I don't know if there is active work going towards making them more relaxed (NLL landed I believe). However, a ton of work has happened to get them out of the way as much as possible.
- skybrian 8y agoIt's useful but I'd like to see a bit more top-level completeness. Every feature should be listed and have at least a cursory description, even if it's not entirely nailed down. (Maybe it already is like that, but the disclaimers say it's not.)
- steveklabnik 8y agoThe vast, vast majority does, but there may be some missing bits. Printed out, it's about 170 sheets of paper, so there's a lot there.