22 Feb
2017
22 Feb
'17
11:02 a.m.
Hi Robert Am 21.02.2017 um 21:41 schrieb Robert Ramey via Boost:
On 2/21/17 10:21 AM, Deniz Bahadir via Boost wrote:
Am 21.02.2017 um 18:07 schrieb Bruno Dutra via Boost:
Our problem is, that we never really used Boost.MPL directly. We just got it for "free" as a (costly) dependency through other Boost libraries (e.g. Boost.MSM).
What's "costly" about it? What are you refering to?
With "costly" I meant the compilation-times and the RAM-usage. (Especially on GCC.) But to be fair, probably it is not only Boost.MPLs fault. Some unlucky decisions on our side concerning the design intensified this.
Robert Ramey
Deniz