zeal VS include-what-you-use

There's also Zeal (https://zealdocs.org/) which is basically the same as Dash but open source and runs on non-Mac devices.

For offline tech documentation you can use Zeal. Must have tool for poor internet connection places. Present in ubuntu repos. https://zealdocs.org/

ads don't have to proprietary

here's one example of ads in FOSS https://github.com/zealdocs/zeal/issues/779

There’s stuff like https://zealdocs.org/ that allow you to take all relevant documentation with you so offline coding will work.

If you just want to be productive, you could also bring a lot of books or downloaded tutorials on a drive.

Btw, make sure your drive is encrypted and you think of a way to backup your data so you don’t lose the offline progress.

I’d suggest you look into Kiwix¹ and also Zeal².

1. https://www.kiwix.org/

2. https://zealdocs.org/

For offline documentation, I use Zeal (called Dash on macos) which looks/works almost identically to rubydoc.info but much faster since it's offline, has a standard interface for all installed language documentations, and only 1 global hotkey away while programming.

I highly recommend using local solutions to this local issue: Zeal[1] (aka Dash[2] on MacOS)

Load up the "docsets" of your languages (lightly edited HTML docs for indexing purposes) and use a global keyboard shortcut (F8 for me) to pull up Python/Postgres/Terraform docs, searching for the right function without internet query.

This isn't straight up applicable to all questions of course, but "How do I search regular expressions in Python again?" is now as easy as "re"

Note that the docsets can be converted from normal HTML ones via doc2dash[3], especially useful to load up custom docs like private providers.

[1]: https://zealdocs.org/

Interesting...how does it compare to https://github.com/include-what-you-use/include-what-you-use ?

Build Insights in Visual Studio, include-what-you-use).

Looks like https://include-what-you-use.org/ might do that.

If you are worried about includes, use https://github.com/include-what-you-use/include-what-you-use and stop thinking about it.

Getting rid of that is not straightforard, though some tools can help with that

You can use the tool https://github.com/include-what-you-use/include-what-you-use to do this for for. It tracks included files and can give comment for what is used from each file. It also warns you when you include files that you don’t use

Invisible imports (e.g. traits). In Python, everything is fully namespaced (unless you from import * in which case all bets are off). It's always explicit where a name is coming from. C is the opposite: #include lets you refer to anything defined in the headers with no namespacing. That's why a common strategy (include what you use) has an associated code style: after every non-std #include you have a comment saying which of its definitions you are using. Of course, Rust is much less implicit, but I still sometimes struggle with traits. For example, you can use tokio::net::TcpStream, but you need to also use tokio::io::AsyncReadExt for the .read trait to be defined on TcpStream. This makes it hard (for me) to answer questions like "what traits are currently available in this scope?" and "why is this module being imported?"

Aside from being closed source and not available on all architectures, how does it compare to iwyu(https://include-what-you-use.org/) or clang's relatively recent include-fixer which is also accessible via clangd?

I set up include-what-you-use and I let it tell me which headers should be where. The IWYU rules would have put all needed headers including in the cpp file.