21 Feb
2023
21 Feb
'23
11:47 p.m.
On Tue Feb 21 23:47:23 2023 +0000, Zebediah Figura wrote:
I guess I didn't quite think the struct tests through; I forgot we use a separate rule to actually define struct types, and so the automated test doesn't prove anything one way or another. A manual test confirms that v4 is correct, though, at least. In my defense, though, that error message is wrong and misled me; we can't be "redefining" anything in that rule. I'll send a patch to fix it.
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.