[karrotwaltz]

The most verbose type of template errors I can think of are instantiation errors with multiple candidates and type deduction failures. In these cases there won't be any elision so it won't help much.

I still hope one day we'll see GCC & clang implement some kind of parsable diagnostic output (e.g JSON). Simply folding all the candidates on a UI would be a massive step forward in reading template errors.

[Uberphallus]

I'll be happy if the mismatching template types are simply aligned in two lines so it's easy to spot the differences.

[jcelerier]

> Simply folding all the candidates on a UI would be a massive step forward in reading template errors.

well... that's already what happens if you use an IDE ? That's at least the case on Qt Creator

[karrotwaltz]

I've heard a lot of good about QtCreator lately, from multiple people, I'll give it a try soon.

Still, some parsable output would be great for many cases, a CI with diagnostic on a web page for example