Ah: you can’t have both classes public. public implies that names won’t be mangled. As soon as i make one of the classes “assembly” (i.e. just remove the public keyword, your project compiles fine.
Ah, I see. Makes sense. Could be worth adding to that to the doc’s / error message ?
It wasn’t actually an issue in my case since the conflicting names were the result of a refactoring exercise - the same class temporarily was in two namespaces while I refactored, but once that exercise was done one of the namespaces (and the class(es) in it) would be retired. So I simply renamed the soon-to-be-retired class to avoid the conflict in the meantime, but was curious as to why the error occurred. Good to know for the future. Thanks.