|
|
Boost : |
From: Stephan T. Lavavej (stl_at_[hidden])
Date: 2024-04-08 19:38:24
[Ruben Perez]
> I have questions regarding this - maybe you can help me here:
> * Let's say I build a Boost module. This #include's std headers in its global module fragment.
> * Now the user compiles their main.cpp, and they import boost and the std modules. No includes here.
> Is this scenario supposed to work? If it is, is it supposed to be portable (i.e. defined by the standard)?
It's supposed to work portably according to the Standard (N4971 [std.modules]).
With our current implementation, this is effectively the include/import mixing that's challenging for MSVC to handle. (May or may not work in VS 2022 17.10. I have a test that ensures that plain #include <meow>​ before import std;​ works, but not more exotic scenarios. Basically anything that leads to the std​ module being dragged in, and then the compiler seeing an #include <meow>​, will result in the compiler seeing duplicate machinery that with the current implementation it cannot reconcile. Having #include <meow>​ be within another module's GMF counts AFAIK.) It would be better for the Boost module to be built on top of the Standard Library Module (both in terms of avoiding current compiler limitations, and for long-term cleanliness and build throughput).
STL
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk