Comment 6 for bug 1746615

> The idea has been that the os-traits package itself is the authority and which version of that
> something has available to it is the controlling factor. This does present the challenge you
> describe but the mechanics of fixing it so that placement becomes the authority for resource
> classes or traits becomes weird: where do the constants that are used in "client" code come from?
>
> It's not always the case that the client is retrieving something from placement. Sometimes it
> just wants to say "I have _this_ resource class and _these_ traits".
>
> What's your expectation there?

For the sake of closure, I wanted to note that cdent and I discussed this (somewhere). I eventually conceded that, whereas the hole I describe is theoretically possible, it's unlikely enough to come up in real life, and would be difficult enough to close, that it's not worth worrying about.