Modules: whether to split up implementation and declaration, or not
Channel
C++Weekly
Topics
With the introduction of C++20 modules, I felt that we could finally step away from splitting up declaration and implementation as we did with header and source files. Yet, I still see many people put module implementation inside separate .cpp files.
What are reasons to keep doing this? What does it mean for compilation speed, incremental build, etc. What's the vision of the standard committee? Are we gonna move more towards languages like Java, C#, and Rust, where there is no split-up, or are they good reasons to keep splitting it up?
Length
Around 10 minutes, I feel.
This is kind of related to https://github.com/lefticus/cpp_weekly/issues/488 , could be part of the same video