https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67499
--- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- > If we were outputting html, it would be much easier, we could print the > error message and have javascript so that clicking in appropriate places > displays the candidates, the reason for substitution failure, what a type is > an alias for, etc. This is something IDEs could do. But with text, we have > to print everything that might be useful. GCC outputting html (or XML: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165#c10 and later comments) seems much more unlikely than someone deciding to implement at least one of my points above. Anyone that needs such HTML output will already use Clang, which had HTML output 6 years ago) instead of spending a few years trying to implement it in GCC.
