Ben Boeckel

There are also things like `#embed` and `std::embed`, so resource files may be of interest here. Other than that, I think just having ways of specifying relevant languages (e.g., a...

The purpose of `X-` fields (though I'm not familiar with their use here) is to be able to also have tools agree on things, similar to OpenGL extensions just being...

I think the `X-` prefix "screams" extension info. `tools/` doesn't really do that.

I think HTTP headers and CSS are the normal culprits there. For the C++20 module dependency format, R0 had a top-level `extensions` object for such purposes. Instead, after discussion, there...

OK, found the minutes. The idea there was that extra information may be useful across the object tree. Trying to annotate a component with an extension CMake companion module in...

I hope it mostly gets used for special-case logic for things like CMake APIs provided by a package or the like (e.g., `FindPython` providing a function to build a Python...

There are some things that cannot be described with declarative code. VTK's autoinit system is one such functionality (intersectional usage requirements that end up generating a header). It's a long...

The way we codified this in other documents in similar fields is to have minor bumps for additional (but non-essential) information, but semantic changes such as additional, non-ignorable information be...

Yes, but the key is to define what "incompatibility" means. Adding a key is technically a minor bump, but adding an unignorable key is a major bump. Surface-level analysis is...

I think once we have CPS working for projects of sufficient complexity, the majority of cases are likely handled. A corpus of such projects off the top of my head:...