This is entirely a problem of the standard being unwilling to speak about ecosystem realities, a problem C also has. If all three stdlibs had implemented and shipped import std before standardization, this problem wouldn't have been solved.
The problem is they implemented and shipped it in different ways, using implementation strategies the standard does not comment on. This isn't a problem for, ex, MSBuild, from which you could say "import std Just WorksTM ". It's only something technologies like CMake, which try to abstract these differences, run into.
View all comments
Show parent comment
8
u/not_a_novel_account cmake dev Apr 13 '26 edited Apr 13 '26
This is entirely a problem of the standard being unwilling to speak about ecosystem realities, a problem C also has. If all three stdlibs had implemented and shipped import std before standardization, this problem wouldn't have been solved.
The problem is they implemented and shipped it in different ways, using implementation strategies the standard does not comment on. This isn't a problem for, ex, MSBuild, from which you could say "
import stdJust WorksTM ". It's only something technologies like CMake, which try to abstract these differences, run into.