Skip to content

Conversation

@dhthwy
Copy link
Contributor

@dhthwy dhthwy commented Nov 12, 2025

We'll see how this goes.

gcc/clang has been lying to me. Seems standard types like std::string don't require an #include in my version.

@dhthwy
Copy link
Contributor Author

dhthwy commented Nov 12, 2025

Of course, that did very little to actually help build times.

@ab9rf
Copy link
Member

ab9rf commented Nov 12, 2025

gcc/clang has been lying to me. Seems standard types like std::string don't require an #include in my version.

gcc's libc++ has a lot of cross-includes such that including one header often pulls in dozens of others. MSTL does this too, but not as much, and with different headers. Obviously neither behavior can or should be relied on.

@dhthwy
Copy link
Contributor Author

dhthwy commented Nov 12, 2025

It was actually the linters I was referring to (namely clangd), and I think it was the templates it was struggling with.

@ab9rf ab9rf merged commit 7952079 into DFHack:develop Nov 16, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants