i have a really interesting refactoring in the works of

CompilerOptionSetsMixin

into a subsystem in itself, which makes it possible for other subsystems to depend on it with a subscoped dependency. this means that instead of having v1 tasks do the work of depending upon a subsystem which mixes in

CompilerOptionSetsMixin

and interpreting it, that the target itself can actually declare a subsystem dependency, and that all the logic for calculating compiler option sets can be done in the target itself. i'm still working on it and will shelve it for a bit, but it was a really fun plane project and i think the result will be that the canonical mechanisms for doing this kind of complex logic (1) can be made super super concise (2) can be totally decoupled from v1 task implementations.