2 ms·
So, the terminology I've used since around 2013: * API documentation: stuff like "type signatures" * Reference documentation: the specification of the languag
by steveklabnik 7y ago
So, the terminology I've used since around 2013:
* API documentation: stuff like "type signatures"
* Reference documentation: the specification of the language
* Tutorials: long-form text that explains things
I gave a talk about the Bay Area Rust Meetup about this, but it seems like maybe it's lost to history :(
Anyway, rustdoc makes this distinction in a sense because it only provides API documentation, which I believe is what you're calling "reference" documentation. mdbook provides the longer form factor.
Most libraries don't have a language spec, since they're not a language, so they have categories one and three.