Skip to content

Aqua.jl reports method ambiguities for InlineStrings.jl methods #64

Open
@brainandforce

Description

@brainandforce

I was considering adding InlineStrings.jl to a package I'm developing that uses Aqua.jl for automated testing, but during the CI run I found this in the report:

3 ambiguities found
Ambiguity #1
unsafe_convert(::Type{Ptr{UInt8}}, x::Ref{T}) where T<:InlineStrings.InlineString in InlineStrings at /home/runner/.julia/packages/InlineStrings/rlLZO/src/InlineStrings.jl:167
unsafe_convert(::Type{P}, x::Ptr) where P<:Ptr in Base at essentials.jl:416

Possible fix, define
  unsafe_convert(::Type{Ptr{UInt8}}, ::Ptr{T}) where T<:InlineStrings.InlineString

Ambiguity #2
unsafe_convert(::Type{Ptr{Int8}}, x::Ref{T}) where T<:InlineStrings.InlineString in InlineStrings at /home/runner/.julia/packages/InlineStrings/rlLZO/src/InlineStrings.jl:169
unsafe_convert(::Type{P}, x::Ptr) where P<:Ptr in Base at essentials.jl:416

Possible fix, define
  unsafe_convert(::Type{Ptr{Int8}}, ::Ptr{T}) where T<:InlineStrings.InlineString

Ambiguity #3
defalg(::AbstractArray{<:Union{Missing, InlineStrings.String1, InlineStrings.String15, InlineStrings.String3, InlineStrings.String7}}) in InlineStrings at /home/runner/.julia/packages/InlineStrings/rlLZO/src/InlineStrings.jl:942
defalg(v::AbstractArray{<:Union{Missing, Number}}) in Base.Sort at sort.jl:655

Possible fix, define
  defalg(::AbstractArray{<:Missing})

Method ambiguity: Test Failed at /home/runner/.julia/packages/Aqua/utObL/src/ambiguities.jl:117
  Expression: success(pipeline(cmd; stdout = stdout, stderr = stderr))

This is going to cause any package that uses Aqua.jl for testing to fail tests if they include InlineStrings as a dependency.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions