Miro Knejp

https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md

Right now disposing is only handled for `IDisposable`. However if a type implements `IAsyncDisposable` the variant should implement that as well and delegate asynchronous disposing to the live value where...

If `System.Collections.Generic.IAsyncEnumerable` exists generate extension methods similar to those for `IEnumerable`.

Determine visibility of generated extension methods based on variant types

2

Currently all generated extension methods are `public` regardless of the visibility of the variant type. Thus the following generates invalid code because the generated extensions have inconsistent accessibility: ```cs namespace...

Currently the generated `static class` containing extension methods is either `public` or `internal` based on the visibility of the variant itself, but it doesn't take into consideration the visibility of...

Currently all generated methods are `public` regardless of the visibility of the contained type. Thus the following generates invalid code because the generated members have inconsistent accessibility: ```cs internal class...

If a variant `class` has no default constructor and all other constructors initialize the `_variant` field to a non-default value then the variant cannot be empty. Under these circumstances the...

If the user already defines certain special methods (like `ToString` or `Equals`) don't generate them. This is currently only supported for `Dispose`. Candidates: - [ ] Constructors - [ ]...

Right now variant classes are only supported at namespace-level. Attempting to create one as a nested class will generate invalid code.

Use sized types in SPIR-V generation

6

The SPIR-V generator currently uses `unsigned int` for all its internal representation. However there is no guarantee for this type to be 32 bits (one SPIR-V word) wide. There are...