4 ms·

I don’t know why the experience for the current top commenter has been so poor, but I absolutely love Rust docs, and it never takes me more than a few seconds o

I don’t know why the experience for the current top commenter has been so poor, but I absolutely love Rust docs, and it never takes me more than a few seconds on the website to find what I am looking for. Perhaps navigating just takes a little getting used to. If something doesn’t make sense to me I can straight away jump into the source code and make sense of it, from a single click. I have learned so much about programming just reading the docs for the standard library, or it’s source code. The documentation is one of my favourite things about it the language.

ptato 7y ago
What do you mean you don't know? The comment explains his experience a fair bit.
OJFord 7y ago
> I don’t know why the experience for the current top commenter Meta: the experience for readers of your comment would be much better if you'd chosen to reply to that not-now-currently top commenter. I think almost certainly it was this: https://news.ycombinator.com/item?id=22636726 https://news.ycombinator.com/item?id=22636726 But that may not be clear at all to later readers if there are many comments here.
asdkhadsj 7y ago
I too find it quite nice. Though when I was starting out I found it exceptionally confusing. Notably the `impl` section towards the bottom. Even today, while I understand that section no problem - I don't usually find it too useful. Likely because the impls in Rust can be a bit weird. Ie Foo might impl `Responder` but only if `Foo` also implements `Serialize`, and those sort of scenarios have happened enough that I usually just ignore the bottom impl section. Not to say that the documentation is incorrect at all, I'm merely explaining how I have "adapted" to scenarios of the past - which could be confusion of my own making. But.. aside from that, I quite like Rust Docs. I also especially love how I can write tests in them, link to other types and modules like `[Foo]`. My complaint list for Rust Docs is surprisingly short honestly. Especially since they fixed the slow page loading on huge impl lists.

ptato 7y ago

What do you mean you don't know? The comment explains his experience a fair bit.

OJFord 7y ago

> I don’t know why the experience for the current top commenter Meta: the experience for readers of your comment would be much better if you'd chosen to reply to that not-now-currently top commenter. I think almost certainly it was this: https://news.ycombinator.com/item?id=22636726 https://news.ycombinator.com/item?id=22636726 But that may not be clear at all to later readers if there are many comments here.

asdkhadsj 7y ago

I too find it quite nice. Though when I was starting out I found it exceptionally confusing. Notably the `impl` section towards the bottom. Even today, while I understand that section no problem - I don't usually find it too useful. Likely because the impls in Rust can be a bit weird. Ie Foo might impl `Responder` but only if `Foo` also implements `Serialize`, and those sort of scenarios have happened enough that I usually just ignore the bottom impl section. Not to say that the documentation is incorrect at all, I'm merely explaining how I have "adapted" to scenarios of the past - which could be confusion of my own making. But.. aside from that, I quite like Rust Docs. I also especially love how I can write tests in them, link to other types and modules like `[Foo]`. My complaint list for Rust Docs is surprisingly short honestly. Especially since they fixed the slow page loading on huge impl lists.