http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45923
--- Comment #11 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 2011-01-20 19:27:27 UTC --- Know this is not high-priority bug for 4.6.0 but it should be as constexpr is a new feature and the initial QoI for diagnostics is important for user's first impressions. Diagnostics are lagging, as this is a new form of C++ diagnostic: there are some interesting opportunities here. We can do better!! I've given some examples, but I'm not quite sure what is required and what Jason and Gaby are thinking in terms of how this stuff should be architected. Thoughts or sketches guys? If a plan can be outlined here in bugzilla, then perhaps it could be split into smaller parts and independently executed?
