Improvements to nullable / boxing #1063
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
manodasanW
commented
Dec 10, 2021
j0shuams
reviewed
Jan 12, 2022
…an nullable object instead with the actual object rather than calling value each time to allow for better caching.
manodasanW
force-pushed
the
manodasanw/nullableperf3
branch
from
d40dbf7 to
6bcfc04
Compare
j0shuams
approved these changes
Jan 21, 2022
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.
Created specialized versions of some of the common nullable types to make use of function pointers rather than delegates and avoid generic marshalers.
Fixed issue with nullable delegates where we can't associate them with 2 different pointers (delegate ptr and nullable ptr) and as part of that also improved how we return back wrapped nullable objects which were used for types and strings and now also used for delegates.
Fixes #87