Matthew Woehlke

On the one hand, it would be good if we could avoid those entirely (i.e. what we said in Slack). On the other, at least in CMake-land, I'm pretty sure...

The `interface` type is the intended mechanism. I'm not *necessarily* wedded to the name, but I don't have any better ideas. In general, the idea of a component specification is...

> Conceptually "Interface" sounds more to me like "We renamed this component, and this 'Interface' maintains backwards compat" or "we have 100 implementation details but 10 supported 'Interfaces'", which sound...

> I think it would be useful to enumerate some of the common uses we envision for "interfaces"; or to mention that header-only libraries would be represented by "interfaces". That...

I'm not sure this is the "right" answer, but the question is very similar to how to deal with threading support, which (at present) is explicitly [a compiler feature](https://cps-org.github.io/cps/features.html#threads). The...

> I prefer this wording [...] Yes, I guess we should change that also, but an empty object *is* a valid Requirement; "or an empty object" is redundant. ``` Values...

> everyone else uses a C library of some kind on Linux ...which is why there is [`C-Runtime-Vendor`](https://mwoehlke.github.io/cps/schema.html#c-runtime-vendor) (and `-Version`, and `Cpp-Runtime-*` and `Clr-*`.) Except for userland (and its not...

As far as stuff like `-ffast-math` and such... yeah... that's not well specified right now (though I believe the hope was that required compile flags would help), because that sort...

Threaded vs. not can be encoded using [`threads`](https://cps-org.github.io/cps/features.html#threads) feature. (Note that I have an open TO DO to check if this is okay as a link-only feature or if it...

I'm pretty sure I had a specific example in mind when I wrote that bit... but I strongly suspect it wasn't a `-Werror=foo` needed, but a `-Wno-error=foo`. (For symmetry, the...