-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Diagnostics for emitted IL code #54
Comments
Ok, it was a lot of words. What exactly should we do:
|
Existing options |
Here is working IL Visualizer for VS 2017: https://github.com/dadhi/il-visualizer |
The produced IL is the same :)
Therefore the difference in calling the delegate. |
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 |
Yep, I was also thinking to add it to readme, time-saver for me, especially in debug. |
The new diagnostics instruments available from the
|
The FEC may generate different IL and therefore may display different execution performance for the result delegate.
There is also question of correctness and easy of debugging.
It also should simplify new features implementation, etc. etc.
Really strange, that the project was able to get to this point without such thing.
For all these purposes we need an ability to dump the resulting IL, so it can be compared with standard IL produced by C# compiler.
The text was updated successfully, but these errors were encountered: