Neal Gafter
Neal Gafter
@odalet > And by the way, maybe the target milestone should be updated: can this be fixed (or mitigated) for 16.6? If you think you could do this with a...
I recommend we don't touch this text in v8. If we need to adjust it in v9, let's revisit it at that time. FYI, the relevant compiler code is in...
That may have been fixed in https://github.com/dotnet/roslyn/pull/37915 which will be in Visual Studio 2019 update 4.
Closing as fixed in 16.4 due to https://github.com/dotnet/roslyn/pull/37915. Please reopen if that is not in fact fixed.
> Is there a way to fix it altogether? This is a limitation of the specification for the assembly file format. We would need to revise that to lift the...
The `#US` "user string" heap in an assembly has a "Size" that is stored as 4 bytes. There are no plans for an overhaul of the assembly file format. If...
@ferbalu22 I think you are confirming that this is fixed in .net core 3.
This is by design (the struct has no accessible fields), but I believe we want to change the design.
Also reported at https://github.com/dotnet/roslyn/issues/39062 and many other places.
I don't think we can solve the problems arising from `null` by introducing new kinds of null.