Re: [boost] "Simple C++11 metaprogramming"

On 2015-08-20 19:50, Bruno Dutra wrote: <snip>

Now lets imagine the user nonetheless tries to evaluate a metafunction that instantiates to "nothing". The only error the compiler will raise will look similar to the following:

error: no type named 'type' in 'struct metafunction'

That's it, no scary internals exposed.

I'm not so sure that's wise. These "scary internals" are often vital hints to debugging when code isn't doing what you expect. How confident are you that such is not needed here? John Bytheway