I'd cast all my votes on this one <3
Yes! It's not as rare as you would imagine that people use Linqpad to do some micro-optimizations or algorithm analysis.
This request is not only about opcodes themselves, but it would make instruction size and arguments more apparent. Reading address offsets is more cumbersome than needed.chojrak11 supported this idea ·
I need some feedback on this feature. First:
(a) Would you expect it to apply only to untitled queries? Or:
(b) Would you also expect it to apply to saved queries that were modified?
(The reason I ask is that option (a) is simple to implement, whereas option (b) creates numerous complications.)
I think it should be similar behavior to what VS Code offers. Saved documents that were modified are just saved, untitled/unsaved documents are persisted in some temp area (in Local portion of user profile) and all of them are reopened next time LinqPad is started, in the same tab order. Thanks.
ALT-S has been fixed (thanks Joe), so I'm removing my votes. Thanks!
Are you aware that you can call .Dump() on an expression? The output is not exactly the same as the Expression Tree Visualizer, but it conveys much of the same information. Is there anything missing from what you see that you’d like added? Or anything that you’d like changed?