TrinityCore VS include-what-you-use

You could take a look at TrinityCore[1] and adjacent projects! Best of luck!

[1] https://github.com/TrinityCore/TrinityCore

TrinityCore: https://www.trinitycore.org/ send email for your questions, or look at this video if you want https://www.youtube.com/watch?v=tAJ0dvNuARs

Trinitycore has 3.4.0 for Wotlk classic but it's pure sandbox. It's so much work to be done so don't expect it to be released. https://github.com/TrinityCore/TrinityCore/tree/wotlk_classic

You can host your own WoW server locally! I would personally recommend TrinityCore. It can be a little bit of a hassle, here's a setup guide.

If they use the base TrinityCore code there's no processing (the whole point of GetAll is a minimal processing dump of the data as-is). You can see the commit for it here https://github.com/TrinityCore/TrinityCore/commit/3aaeb574050668e5a240078f6e40337c3975d110 and you can see it just dumps what is there until 55k then stops hard.

You can just compile one here - https://github.com/TrinityCore/TrinityCore

TrinityCore, AzerothCore- C++, these and others like them are the server for projects- well-known for being used on private WOW servers, so they're probably good enough for your personal project https://www.libhunt.com/r/TrinityCore - https://www.trinitycore.org/ - https://www.azerothcore.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.