Neat! This is sort of a hash tree fixed at two levels, as I see it (from my cursory reading.)
Question: I have always stayed away from Boost stuff on the assumption that using any one class from it will drag in a ton of other dependencies, ballooning my build time and possibly code size. Is this still true?
Unfortunately, yes, it’s still true. In fact, it’s not that you get half of Boost with any library, but you get some dependencies that don’t make any sense. For example, Boost.Graph depends on Boost.Regex (and thus ICU) apparently because Boost.Graph parses some obscure data format using regex.
Neat! This is sort of a hash tree fixed at two levels, as I see it (from my cursory reading.)
Question: I have always stayed away from Boost stuff on the assumption that using any one class from it will drag in a ton of other dependencies, ballooning my build time and possibly code size. Is this still true?
Unfortunately, yes, it’s still true. In fact, it’s not that you get half of Boost with any library, but you get some dependencies that don’t make any sense. For example, Boost.Graph depends on Boost.Regex (and thus ICU) apparently because Boost.Graph parses some obscure data format using regex.