On Tue Feb 21 23:47:23 2023 +0000, Nikolay Sivov wrote:
Maybe it's worded like that because of the error message that Windows produces - "redefinition of type with struct/class". It's probably a side effect of something else happening in type name collision, obviously this can't define a new type. Using unique name will give another error right away.
Ah, that'd make sense.