Correctly process inline signatures #167
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… and writing a correct signature as a blob on method body writing.
…logic from the last commit.
vermorel
approved these changes
May 25, 2022
|
@OlegRa This was tricky one! Thank you very much for this contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Inline signatures used by the
calliMSIL instruction are part of a new high-performance low-level unsafe platform interop (function pointers indelegate*format). The current implementation handles most of the practical use cases except the single one: function pointers as arguments of function pointers. I'll open a separate issue for this use case (very rare). This PR completely covers and fixes #106.