invoke should raise MethodError for ambiguous cases #18095
Labels
bug
Indicates an unexpected problem or unintended behavior
types and dispatch
Types, subtyping and method dispatch
Milestone
Currently we have this:
When
invoke
is called with an ambiguous tuple of types, it should raise the same error as when the function is simply called with arguments of those types. Discovered while playing with the@invoke
macro I cooked up here.The text was updated successfully, but these errors were encountered: