Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering, why is the difference with OpCodes.Tailcall? (I could't find any info about
OpCodes.Tail
in the docs).And also, does this optimization work for all calls or for the recursion calls only?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah,
OpCodes.Tailcall
is correct vor .NET (fixed the code)And
.Tail
is forCecil
library used in DOIt works only before sequence
call
,ret
And this is not always recursive
I have already applied such change before and then reverted it c67bd84
My new understanding based on Debugger & StackTraces from dumps is:
Without
.tail
prefix the JIT optimizer SOMETIME can guess to do it, but not in 100% cases.tail.
prefix guarantees this kind of optimization