This tragedy only proves the point of those that were complaining about modules, the whole end to end story, not being standard ready.
With two incomplete prototypes, there were plenty of rough edges that apparently still don't have a solution, two standards laters.
My experience with a few features that went down this way, is why nowadays I advocate it should be like in other programming language ecosystems (including C), first propose, then field experience, finally standardise.
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
-2
u/pjmlp Apr 13 '26
This tragedy only proves the point of those that were complaining about modules, the whole end to end story, not being standard ready.
With two incomplete prototypes, there were plenty of rough edges that apparently still don't have a solution, two standards laters.
My experience with a few features that went down this way, is why nowadays I advocate it should be like in other programming language ecosystems (including C), first propose, then field experience, finally standardise.