Hacker News Reader

Comment by domenicd | Hacker News Reader

What type of project actually uses C++ 23 modules in real life? What kind of toolchain enables that? When I worked on Chromium, they were indefinitely in the "maybe in 5-10 years the tooling will be ready" camp.

View on HN

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

What early adopters are using them? Because my impression is the tooling still isn’t there

CMake says they are there. Other tools mostly are not.

Nobody has said they are using them in anything important, but hopefully that is coming.

CMake has support for named modules but does not support header units or C++23 module features such as import std;

Import 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.

We 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.

People using Visual C++ with MSBuild, or clang with CMake and ninja.

It’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.

Yeah, 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.

Projects: https://arewemodulesyet.org/projects/

Tools: https://arewemodulesyet.org/tools/

C++20 is pretty common and gives you already a pretty nice engineering experience.

YC startup. Toolchain was Clang and sh.

Chromium is gonna be more conservative than that for sure.

Reply on news.ycombinator.com