On Fri, Nov 3, 2017 at 7:58 PM, James E. King, III wrote:
I have an open defect related to a random seed generator that's currently in boost::uuids::detail called seed_rng. The class does a fair bit more than it really needs to, and does not support Universal Windows Platform (UWP) store targets. It is otherwise quite similar to boost::random::random_device however it is a header-only implementation (in fact seed_rng has a comment about putting it into Boost.Random). I was planning on removing it and leaving randomness to Boost.Random because that's where the code really belongs, however this would introduce a new library dependency on Boost.Random for any code using boost::uuids::random_generator. So I'm curious on how important folks believe it is to maintain the header-only status of Boost.Uuid.
While I don't use Boost.Uuid, I do think users of Boost enjoy the convenience of header-only libraries (and know of at some who are restricted to - within their organization - only the header-only libraries). Why not make Boost.Random header-only first, before taking the dependency on it? Glen