You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a module interface that just includes and exports the entire header file
This is fragile but apparently works totally fine on newer compilers.
Provide a module interface that includes the header file, then selectively exports what it needs
This is more "correct" but also a very difficult task.
The nuclear option would be to bump the minimum to C++20 and switch to using pure modules. I can already feel the angry looks from the boomers. I would not recommend this unless you have a death wish, or if the entire world decides to switch to modules overnight.
This would be a huge help for my projects that use this, as I am trying to push modules as far forward as possible.
Not going to bump to min c++20, nor switch to a modules only interface. This isn't about "boomers", it is about backward compat and supporting projects that have decades of history using this project.
Creating a new module interface based on importing the existing header seems possible. I'm thinking something like the following, with different modules for the different converters, generic/win32/icu.
Since this matters to you, why don't you put this together in consumer code, and tell me how it works out for you. Let me know what issues you have, and then create a PR with any suggested changes needed (that still provide backward compat).
Activity
brofield commentedon Nov 18, 2026
Not going to bump to min c++20, nor switch to a modules only interface. This isn't about "boomers", it is about backward compat and supporting projects that have decades of history using this project.
Creating a new module interface based on importing the existing header seems possible. I'm thinking something like the following, with different modules for the different converters, generic/win32/icu.
Since this matters to you, why don't you put this together in consumer code, and tell me how it works out for you. Let me know what issues you have, and then create a PR with any suggested changes needed (that still provide backward compat).