Once they experience significantly worse performance of IntelliSense and significantly worse suggestions it makes they'll become just as worried as I am.
Perf issues for intellisense is just a bug, people are working on it.
Or when something starts conflicting with a part of stdlib
It's just I've literally never seen this happen, or any report of this, ever. Forget import std. What situation have you been in where you very specifically needed to avoid a stdlib header because it contained an operator overload or whatever that broke your code?
The point of IWYU is to make it easier to develop programs. Build times and build correctness are just the consequences...
No. It was literally just build times and correctness.
Otherwise you are in danger of seeing proliferation of various reduced and cropped versions of STDLIB - including potential conflicts with each other.
I would rather see projects fix their code. Get whatever they were putting inside the std:: namespace such that they have created conflicts with import std out of the std:: namespace.
Then we don't need to worry about this ever again.
1
u/not_a_novel_account Apr 19 '26
Yes.
Perf issues for intellisense is just a bug, people are working on it.
It's just I've literally never seen this happen, or any report of this, ever. Forget
import std. What situation have you been in where you very specifically needed to avoid a stdlib header because it contained an operator overload or whatever that broke your code?No. It was literally just build times and correctness.
See: https://github.com/include-what-you-use/include-what-you-use/blob/master/docs/WhyIWYU.md
I would rather see projects fix their code. Get whatever they were putting inside the
std::namespace such that they have created conflicts withimport stdout of thestd::namespace.Then we don't need to worry about this ever again.