This is an MWE simplified from some code that tries to implement * for a type and AbstractStrings. In this MWE, the intention is to return a Foo whenever any argument is a Foo. Is this a bug, or user error? I think that the * method should be more specific than the *(s1::Union{AbstractChar, Abstra…

Like you said, Base doesn’t have a *(::AbstractString, ::AbstractString...) method. Replace that 3rd method and you find: julia> f(s1::Union{AbstractChar, AbstractString}, ss::Union{AbstractChar, AbstractString}...) = 0 f (generic function with 3 methods) julia> f("h", "i") ERROR: MethodError: f(:…

Fatal: error thrown and no exception handler available for a * method

General Usage

oheil August 28, 2023, 8:09am 2

Topic		Replies	Views
Why is this a method ambiguity? General Usage	2	572	January 16, 2017
Could type ambiguity based on `Union` of concrete types be eliminated? General Usage multidispatch , methods , ambiguities	4	240	March 4, 2025
Function signature doesn't match when using Union General Usage	3	589	May 30, 2018
Unexpected ambigiuity in subtype constructor General Usage question , parametric-methods , constructors	2	362	May 4, 2022
Possible bug with dispatch on parametric abstract type General Usage	9	318	May 15, 2023

Fatal: error thrown and no exception handler available for a * method

Related topics