C++ Modules Are Here to Stay

#1

Post by faresahmed » Sat, Jan 24, 2026, 6:49 AM UTC

Re: C++ Modules Are Here to Stay

#2

Post by whobre » Thu, Jan 29, 2026, 6:52 PM UTC

> auto main() -> int {

Dude…

#3

Post by on_the_train » Thu, Jan 29, 2026, 6:55 PM UTC

whobre wrote: post #2

> auto main() -> int { Dude…

It's been the go-to syntax for 15 years now

#4

Post by cmovq » Thu, Jan 29, 2026, 7:05 PM UTC

Can someone using modules chime in on whether they’ve seen build times improve?

#5

Post by feelamee » Thu, Jan 29, 2026, 7:09 PM UTC

why use modules if PCH on your diagram is not much worse in compile times?

#6

Post by CamperBob2 » Thu, Jan 29, 2026, 7:16 PM UTC

whobre wrote: post #2

> auto main() -> int { Dude…

It's like calling a Ford Mustang Mach-E the "Model T++."

#7

Post by reactjs_ » Thu, Jan 29, 2026, 7:24 PM UTC

Here’s the thing I don’t get about module partitions: They only seem to allow one level of encapsulation.

    Program
    - Module
      - Module Partition

whereas in module systems that support module visibility, like Rust’s, you can decompose your program at multiple abstraction levels:

    Program
    - Private Module
      - Private Module
        - Private Module
        - Public Module
      - Public Module

Maybe I am missing something. It seems like you will have to rely on discipline and documentation to enforce clean code layering in C++.

#8

Post by w4rh4wk5 » Thu, Jan 29, 2026, 7:26 PM UTC

https://arewemodulesyet.org/ gives you an overview which libraries already provide a module version.

#9

Post by few » Thu, Jan 29, 2026, 7:31 PM UTC

whobre wrote: post #2

> auto main() -> int { Dude…

And their code example doesn't actually return a value!

#10

Post by Davidbrcz » Thu, Jan 29, 2026, 7:33 PM UTC

few wrote: post #9

whobre wrote: post #2

> auto main() -> int { Dude…

And their code example doesn't actually return a value!

For main it's explicitly allowed by the standard, and no return is equal to return 0