Boris Kolpackov

> you can easily take everything in single-header and place it with `ctre/` prefix into `/usr/include` that's the intended usage anyway That could work (we wouldn't even need the `ctre/`...

Thanks for the offer to change the tests. Regarding `unicode-db.hpp` in `single-header/`: if it is part of the official interface, then we still have the naming issue. Do you think...

I took a look at the `simple` example and have two immediate issues: 1. Module interface units use the same extension (`.cpp`) as module implementation units, non-modules, and non-modular code....

> Why is it a hard requirement? Module code is still C++ code. We made it a hard requirement in `build2` because we strongly believe this is the right thing...

Yes, that sounds reasonable, thanks. Any chance you can grant me write access to this repository? I could then modify `build2`-related stuff directly as well as help out with other...

Yes, I am aware. And MSVC has chosen `.ixx`. Also note that Clang currently uses `.cppm` for their flavor of modules which are quite different compared to what's proposed. So...

Yes, I was planning to look into this when I had a chance, but if you want to take a stab at it, I would be grateful. We can discuss...

Yes, that was my thinking as well! If we want to get a bit fancies, we can use https://download.build2.org/toolchain.sha256 to make it version-independent. It is safe to assume `build2-install-*.sh` pattern...

@mathstuf Hm, wouldn't you want the `Dockerfile`/CI to use the latest released version of `build2`? Failed that, we will have to (remember to) update it every time we make a...

Ok, I see your point.