ModuleInitializerAttribute source generated, causing conflict

[AArnott]

You predicted it, and it happened. I'm using "PolySharp" in my test project already and it's generating the ModuleInitializerAttribute for me, but then your TUnit.Core.SourceGenerator comes along and emits it as well, causing a CS0101 error:

The namespace 'System.Runtime.CompilerServices' already contains a definition for 'ModuleInitializerAttribute'

Is there a way to turn yours off? (I thought you'd decided to not emit this, and rather to document that users may need to reference or declare a polyfill themselves).

[AArnott]

I was able to workaround this by defining my own (3rd, ironically) polyfill as an ordinary source file:

namespace System.Runtime.CompilerServices;

[AttributeUsage(AttributeTargets.Method, Inherited = false)]
internal sealed class ModuleInitializerAttribute : Attribute;

This gets both source generators to stop emitting it, avoiding the collision.

Still, it adds friction (and the workaround isn't particularly discoverable if you're not fluent in how source generators may work) to migrating to TUnit.

[thomhurst]

Maybe adding a project property would be useful to disable it?

<EnableTUnitPolyfills>false</EnableTUnitPolyfills>