(In reply to Zhihao Yuan from comment #11)
> 1. Adjust the error message to say, "The first non-inline, non-pure function
> may not have a definition in <Class>."
That error comes from the linker. The linker is not part of GCC, so this is the wrong place to ask for linker changes.
> 2. Add extra information to name the key function, and pass it to the
> linker, generate an error message to match MSVC's quality.
That's what comment 7 suggested. Comment 10 links to the response to that.
(In reply to Zhihao Yuan from comment #11)
> 1. Adjust the error message to say, "The first non-inline, non-pure function
> may not have a definition in <Class>."
That error comes from the linker. The linker is not part of GCC, so this is the wrong place to ask for linker changes.
> 2. Add extra information to name the key function, and pass it to the
> linker, generate an error message to match MSVC's quality.
That's what comment 7 suggested. Comment 10 links to the response to that.