Overload resolution improvements #377
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
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.
Fixes: #134
Fixes: #352
When JS calls a .NET method that has multiple overloads, the marshaller must resolve the best overload before invoking the method. Previously the overload resolution logic was pretty basic: it only considered the number of arguments and their JS value-types. This change makes the overload resolution much more sophisticated, so that it should work for almost all cases. It's still not perfect, but probably never can be due to the imperfect mapping between JS and .NET types.
See the updated
overloaded-methods.mdfor further description.This also fixes a bug when marshalling a JS
Setobject as .NETICollection<T>.