A good talk on yet another "new" (ahem, see my other comment) feature for C++. I found the speaker to be a bit slow and dragging. Playback at 1.5x speed is much better.
Thx for the talk. How do I consume a modularized library inside an app? I.e. what used to be a shared lib+headers is now a bunch of proprietary binary files.
Afaik nothing much changes here, except that you'd likely ship some module files + binary instead of headers + binary for an SDK. Though its an interesting question.
Compiling headers while being the majority of the sources, is a very small part of the total compile time. We already have pre-compiled headers, and while it is faster, it is not a lot faster.
As the video covers, there's some other good reasons to do this regarding code safety that precompiled headers don't address. These are more important to me than compile speed. I recall 1980s and 1990s C header files defining FALSE as 0 and TRUE as something else, maybe 1, maybe -1, maybe ~FALSE, but they were inconsistent. and the name redefining when including several such files (as parts of "unrelated" libraries from different vendors) can cause problems. This (modules) is the kind of thing that should have been done back then. I recall UCSD Pascal had similar (precompiled) modularization called Units from the late 1970s.
It will depend largely on what you're comping, but "very small" is *in general* somewhat of an exaggeration. Running clang with -ftime-trace is interesting and educational, FWIW.
A good talk on yet another "new" (ahem, see my other comment) feature for C++. I found the speaker to be a bit slow and dragging. Playback at 1.5x speed is much better.
Thanks for the 1.5x hint. She finished strong though!
Thx for the talk. How do I consume a modularized library inside an app? I.e. what used to be a shared lib+headers is now a bunch of proprietary binary files.
Afaik nothing much changes here, except that you'd likely ship some module files + binary instead of headers + binary for an SDK. Though its an interesting question.
@@MeetingCPP Which module files are you referring to? The source files or the CMI files?
beautiful slides! Are they made by latex or powerpoint?
Thanks for the presentation. I wish it was more example driven than top down instruction manual style.
I guess that wasn't feasible in 2019...
Compiling headers while being the majority of the sources, is a very small part of the total compile time. We already have pre-compiled headers, and while it is faster, it is not a lot faster.
As the video covers, there's some other good reasons to do this regarding code safety that precompiled headers don't address. These are more important to me than compile speed. I recall 1980s and 1990s C header files defining FALSE as 0 and TRUE as something else, maybe 1, maybe -1, maybe ~FALSE, but they were inconsistent. and the name redefining when including several such files (as parts of "unrelated" libraries from different vendors) can cause problems. This (modules) is the kind of thing that should have been done back then. I recall UCSD Pascal had similar (precompiled) modularization called Units from the late 1970s.
It will depend largely on what you're comping, but "very small" is *in general* somewhat of an exaggeration. Running clang with -ftime-trace is interesting and educational, FWIW.
Good talk.
and we now can have a cross dependency without lending ur soul to the devil and diving into the hella sketchy preprocessor woodoo stuff.