3 ms·
The tooling people have - as of about a year ago said they are ready. Now everyone who considers themselves early adopters is using then. Most are waiting for t
by bluGill 5mo ago
The tooling people have - as of about a year ago said they are ready. Now everyone who considers themselves early adopters is using then. Most are waiting for the early adopters to figure out what the best practices are so we don't make a mess
- maccard 5mo agoWhat early adopters are using them? Because my impression is the tooling still isn’t there
- bluGill 5mo agoCMake says they are there. Other tools mostly are not. Nobody has said they are using them in anything important, but hopefully that is coming.
- Maxatar 5mo agoCMake has support for named modules but does not support header units or C++23 module features such as import std;
- bluGill 5mo agoImport std has been there for a while but is experimental until gcc supports it. Gcc just for that support so it should be mainline soon.
- maccard 5mo agoWe are now getting close to the distance between c++03 and C++11 for making basic modules work on main line toolchains and build systems. That’s absolutely wild.
- pjmlp 5mo agoPeople using Visual C++ with MSBuild, or clang with CMake and ninja.
- maccard 5mo agoIt’s been 6 months but last time I checked neither IntelliSense nor clangd worked with modules. The build tools have been just about functional for a while though, you’re right.
- pjmlp 5mo agoYeah, Intelisense is a bummer, but you really need VS proper, nor VSCode, which I assume given the clangd reference. Whereas one kind of works (VS), there is apparently no work going on VSCode Intelisense, ticket is stalled since January, and the promised announcement never came up.