3 ms·
Compare with Go's language spec, which is written in a formal (but readable) style with little math. I wouldn't want it to have examples because it's good that
by skybrian 8y ago
Compare with Go's language spec, which is written in a formal (but readable) style with little math. I wouldn't want it to have examples because it's good that it's concise.
One way to start might be to have an official extended cheat sheet. A cheat sheet needn't explain everything, but it should list every language feature available. The idea is to give you a definitive "inventory" of everything available so you can search for answers elsewhere if you see something you don't understand. It should also be brief enough for the language maintainers to commit to updating it when they enable new features.
- lambda 8y agoThanks for the reference to the Go spec (link for the lazy: https://golang.org/ref/spec https://golang.org/ref/spec) It is actually fairly comparable to the Rust Reference (https://doc.rust-lang.org/reference/introduction.html https://doc.rust-lang.org/reference/introduction.html), though the way the Rust Reference is divided into chapters makes it a bit hard to see everything at once or search. They both do contain some examples, as well as things like the syntax in a BNF like format. Perhaps what I'm looking for is just to have the Rust Reference made a bit more complete and a little more accessible in format (the division into chapters doesn't really seem to help much), as well as improving the SEO since it doesn't show up in Google searches often.
- steveklabnik 8y agoThe reference has a search function, if you use the little magnifying glass at the top. You can also use the print option to see it all on one page, if you prefer.