Peter Dimov
Peter Dimov
The more I think about this, the more it seems to me that when a type matches more than one of these categories, the result should be a compile error....
> I think instead of having N independent checks that are either true or false, you could have one variable template whose value is an enum that specifies the conversion...
Looks nicer. Why do we have to include mp11.hpp in the GMF though? Can't we attach things to the named module?
I don't understand why we'd need `` in the GMF, and I also don't understand why we'd need to revert to the export macros. Are we aiming to support configurations...
(2), I think.
As far as I can see that's just ``` template using mpl_eval_if = typename mp_if::type; ```
Ah, right, it needs to be ``` mp_if< cond1, mp_if< cond1_1, true1_1, false1_1 >, mp_if< cond1_2, true1_2, false1_2 > > ``` Mp11 has `mp_cond` that implements the equivalent of an...
Not sure why nesting mp_defer wouldn't work. E.g. here you aren't SFINAE-ing properly at top level because of the unconditional nested type, but I don't see why an mp_defer there...
> Most Boost.MP11 constructs are eager to instantiate their template parameters, and trying to prevent that is really painful. Pretty much all. Mp11 is alias based, and aliases are always...
Support for `std::chrono::duration` should be built-in. `time_point` is maybe trickier. Or maybe not.