Closed ayakael closed 2 years ago
EDIT: Alright. You already posted your issue in dotnet/roslyn issue tracker. My comment here is therefore moot. Lets see how the roslyn folks respond...
Yeah, but that would be a Roslyn problem more than anything else. If some source code trips up a compiler like that, that's a bug in the compiler. Therefore, in my opinion, your problem report would be better placed at https://github.com/dotnet/roslyn/issues.
Copy that, will close for now as indeed I agree that this is more likely to be a roslyn thing.
Looking for guidance on how to debug this.
Version of Roslyn used: 4.4.0-2.22426.8 Steps to Reproduce:
Expected Behavior: Build should work
Actual Behavior:
Also reproducible when building roslyn 4.3.0-3.22415.1 with dotnet sdk 6.0.401 (roslyn 4.3.0-3.22415.1)
Full log newtonsoft.log