Quoting Jonathan Wakely <jwakely....@gmail.com>:
Of course, such a thing could be done by some GCC plugin, but I
believe providing the
feature inside GCC itself, and documenting the format of the
textual type annotation
file, would give this feature more visibility, and it would help
people a lot. And I am
pretty certain that the C++ frontend does compute the type of each
expression, so it is
mostly the point of defining a textual type annotation format and output it.
What's the point of plugins if they aren't used to do this sort of thing?
I think the right balance if good visibility is considered important would be
to have this as a plugin that is shipped with the gcc distribution and
installed by default.
That gives the plugin benefits of not impinging on the memory footprint or
stability of the compiler when not used, and it can also serve as a plugin
example.
We could have a documentation section for plugins shipped with gcc.
