Re: [boost] On Boost and modules

Yes, definitely a module per library. I would avoid the sub-modules. Probably not worth the pain and it would be more confusing to users.

Agree. The only point where they may be necessary is for peer dependencies. For instance, Boost Asio has a peer dependency on OpenSSL, but there are plenty of uses that don't require it (it's not even in the convenience header). I'd advise against the global "boost" module. I don't think it adds anything when you can "import boost.asio" and go.