Well, this kind of attitude is just sad. Rather than imagining issues .NET has without verifying them first and then complaining, I'd like to suggest to spot c

Well, this kind of attitude is just sad. Rather than imagining issues .NET has without verifying them first and then complaining, I'd like to suggest to spot check assumptions with Godbolt[0] which would be a good start (it can't show DynamicPGO, NativeAOT-specific and some other opts but is still fairly illustrative). A more comprehensive view of produced asm can be acquired with [DisassemblyDiagnoser] attribute when running code with BenchmarkDotNet [1] (in the Java world a similar solution is called JMH). [0] https://godbolt.org/ https://godbolt.org/ [1] https://benchmarkdotnet.org/articles/guides/getting-started.html https://benchmarkdotnet.org/articles/guides/getting-started....