Ambiguity in vcat on master / upcoming 1.10.

[KristofferC]

From PkgEval: https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/46617e5_vs_0ba6ec2/SemiclassicalOrthogonalPolynomials.primary.log

  MethodError: vcat(::Vector{Float64}, ::Zeros{Float64, 1, Tuple{InfiniteArrays.OneToInf{Int64}}}) is ambiguous.
  
  Candidates:
    vcat(a::AbstractVector, b::FillArrays.AbstractFill{<:Any, 1, <:Tuple{InfiniteArrays.OneToInf}})
      @ InfiniteArrays ~/.julia/packages/InfiniteArrays/UOszV/src/InfiniteArrays.jl:112
    vcat(X1::Union{Number, AbstractVecOrMat{<:Number}}, X::Union{Number, AbstractVecOrMat{<:Number}}...)
      @ SparseArrays /opt/julia/share/julia/stdlib/v1.10/SparseArrays/src/sparsevector.jl:1235
  
  Possible fix, define
    vcat(::AbstractVector{<:Number}, ::FillArrays.AbstractFill{<:Number, 1, <:Tuple{InfiniteArrays.OneToInf}})
  
  Stacktrace:
    [1] pad(c::Vector{Float64}, ax::InfiniteArrays.OneToInf{Int64})
      @ InfiniteLinearAlgebra ~/.julia/packages/InfiniteLinearAlgebra/pla7L/src/InfiniteLinearAlgebra.jl:110

[jishnub]

Arises from type-piracy in SparseArrays:

JuliaSparse/SparseArrays.jl#431

[KristofferC]

Yes, the situation is unfortunate and likely occurs from historical reasons where SparseArrays was not even an stdlib. I don't think a perfect solution is possible in a reasonable time frame so some workaround / compromise has to be done.

[jishnub]

Closing, as this should be solved now