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.