AStarDemo VS TextLayoutSampler

However, how it is done is compiler specific, see here for an example. The business logic is a static library.

Yes, see https://github.com/pjmlp/AStarDemo/tree/master/AStarDemoLib

Nothing serious, but you can look at

https://github.com/pjmlp/ppm2png

https://github.com/pjmlp/AStarDemo

I am also in the process of porting Raytracing Weekend to C++ modules.

I have another one where I use them, https://github.com/pjmlp/AStarDemo.

This toy project kills IntelliSense, is unable to use static analysers and given the dependency of C++/WinRT on PCH (which cannot be used on projects with modules), it makes exactly the opposite in desired build times.

All of them :b (TextLayoutSampler, FontSetViewer, Onnx2Text, LunaSvgSampleTest, BiNums). With the exception of multicolor fonts (e.g. Segoe UI Emoji) and more robust vertical text support for Japanese text, there just haven't been any new APIs since Windows 7 that warrant moving forward for me 🤷‍♂️. Note all of those are fully C++ based, but I'm also working on a pixel format viewer for which I want C# interop to potentially utilize existing Paint.NET imaging/effect plugins.

I appreciate that you support multiple libraries/file types for the backing serialized text tree representation, for I always thought it silly that configuration tools would often support only a single file type - interop matters! (I had something similar for one of my apps, a general text tree class where the input/output can be JSON/XML/INI)

I can identify with that pain. I first started modularizing one of my projects in 2017, and after reporting another bug, I'd try every new VS release, only to make it another 20% further in the build and encounter another internal compiler issue. Though, it did finally build 100% in VS 2019, consuming Windows.h, some DirectX headers, and various std headers. Boost though, that might still be a beast of complexity beyond.

Well I haven't seen that one, but I've gotten other ICE's and linker errors while incrementally modularizing this app over the years. e.g. Common.Variant.ixx(106,1): fatal error C1001: Internal compiler error. I definitely want to file bugs, and have been, but it's tedious to narrow down the ~20'000 line program for a repro 😑, as often times the change is due to elsewhere rather than the reported line itself. I did though get another program of mine (~15'000 lines) completely modularized successfully yesterday with VS2019 16.10.0 Preview 2, after applying the work-around for one linker error and disabling PCH's with modules. 😊 So it's definitely improving.