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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change error message when throw when same functions are registered #229
Change error message when throw when same functions are registered #229
Changes from all commits
884a311
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Given the issue description I thought that we should throw
AmbiguousDelegateInvocation
whenapplicableMethods.Length > 1
. Why we throw when== 0
?Maybe I missing something .
@metoule maybe you can help us ;-)
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.
That's precisely the issue I highlighted, and why it's actually quite difficult to fix properly :D
The issue resides in the
FindBestMethod
method. When there are multiple applicable overloads, they're filtered thanks to theMethodHasPriority
method, which can also result in an empty array if no overload has the priority:The issue is that the caller of
FindBestMethod
doesn't know if the resulting array is empty because no function was found, or if multiple applicable overloads were found.We might be able to fix the issue like this, but it would require checking all calls to
FindBestMethod
to be sure: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.
I like it. Thank you for the explanation. @sagilio Do you think you can review the code to follow this suggestion?
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.
Thank you for the explanation, I already understand why to return 0 length array here. I think #231 has fixed this well, and will not have much performance impact when the overloads count is not very large.