-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
which should give better error on ambiguous method #47322
Labels
error messages
Better, more actionable error messages
Comments
apaz-cli
added a commit
to apaz-cli/julia
that referenced
this issue
Oct 27, 2022
Error messages for `MethodError` are much more helpful in determining why the method was not successfully dispatched than simply "No unique matching method found." Fixes JuliaLang#47322
apaz-cli
added a commit
to apaz-cli/julia
that referenced
this issue
Oct 28, 2022
Error messages for `MethodError` are much more helpful in determining why the method was not successfully dispatched than simply "No unique matching method found." Fixes JuliaLang#47322
maleadt
pushed a commit
to apaz-cli/julia
that referenced
this issue
Nov 18, 2022
Error messages for `MethodError` are much more helpful in determining why the method was not successfully dispatched than simply "No unique matching method found." Fixes JuliaLang#47322
vtjnash
pushed a commit
that referenced
this issue
Feb 1, 2024
The `MethodError` printing has detailed text on what failed about this dispatch, which can be useful to someone trying to understand why `which` failed, given that `which` is simply a model of the dispatch done by `invoke`. Reuse that printing, but add a short custom header to it and convert to an ErrorException, per triage discussion that this would be clearest. Also add more text to `MethodError` to guide new users in interpreting the exact meaning of some of the cryptic text. Fixes #47322
vtjnash
pushed a commit
to apaz-cli/julia
that referenced
this issue
Feb 1, 2024
The `MethodError` printing has detailed text on what failed about this dispatch, which can be useful to someone trying to understand why `which` failed, given that `which` is simply a model of the dispatch done by `invoke`. Reuse that printing, but add a short custom header to it and convert to an ErrorException, per triage discussion that this would be clearest. Also add more text to `MethodError` to guide new users in interpreting the exact meaning of some of the cryptic text. Fixes JuliaLang#47322
vtjnash
pushed a commit
that referenced
this issue
Feb 3, 2024
Error messages for `MethodError` are much more helpful in determining why the method was not successfully dispatched than simply "No unique matching method found." Fixes #47322
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Calling an ambiguous method gives a nice error message. Calling
which
on it does not:From #22988.
The text was updated successfully, but these errors were encountered: