undefined | Better HN

0 pointscsomar1y ago0 comments

I am not sure if we are speaking about the same thing. LSP can give you type hints. What I am doing is that I am opening a "window" in my editor that has the full docs. You can browse through it freely. The issue with "non-Rust" languages is that the docs will be on a website. On most Rust projects (90%+), the libraries will use the Docs system which makes the docs fully available on LSP.

0 comments

3 comments · 2 top-level

hamandcheese1y ago· 1 in thread

I believe the distinction is that if you have to manually browse the docs and navigate to the method of interest, you might see something else interesting along the way.

Whereas if your editor takes you directly to the method in question, you miss that opportunity.

powersnail1y ago

If I want to read through the doc, I'll just do that, and I frequently do it with all dependencies that I'm directly interacting with. As fun and informative as it is, personally I don't want to do this exercise every time I need a peek at the documentation of a class or function, in the same way I don't take a detour into the mountain every time I get out of my house, as much as I enjoy hiking.

bdhcuidbebe1y ago

> The issue with "non-Rust" languages is that the docs will be on a website.

We have tooling for offline docs of course. See dash (macOS) or zeal (win/linux)

j / k navigate · click thread line to collapse