Diagnostics for emitted IL code about fastexpressioncompiler

[dadhi]

Existing options

1. https://github.com/drewnoakes/il-visualizer
2. https://github.com/bartdesmet/ExpressionFutures/tree/master/CSharpExpressions/Tests.Microsoft.CodeAnalysis.CSharp.Helpers/ILVisualizer
3. https://github.com/longda/roslyn/tree/89169a3380e48fc834c72e38355867881d030e94/Src/Test/PdbUtilities/Metadata

[dadhi]

Ok, it was a lot of words. What exactly should we do:

1. Output the IL for fast compiled delegate.
2. Output the IL for normally compiled delegate.
3. If possible output target Asm for both.
4. IL output obviously should not affect compilation performance.

[dadhi]

Here is working IL Visualizer for VS 2017: https://github.com/dadhi/il-visualizer

[dadhi]

The produced IL is the same :)

IL_0000: ldarg.1    
IL_0001: ldarg.2    
IL_0002: add        
IL_0003: ret        

Therefore the difference in calling the delegate.
I have an idea to test 3 parameters delegate with first empty Closure argument instead of static delegate with 2 parameters.

[dzmitry-lahoda]

My current approach:

https://en.wikipedia.org/wiki/List_of_CIL_instructions

[dzmitry-lahoda]

2017 support https://github.com/drewnoakes/il-visualizer merged into main repository. So may star and use only that. It seems nice helper to add into contibuting part of readme. bartdesmet does intresting work regarding expression so.

[dadhi]

Yep, I was also thinking to add it to readme, time-saver for me, especially in debug.

[dadhi]

The new diagnostics instruments available from the TestTools class:

• PrintIL()
• PrintCSharpString()
• AssertOpCodes()