this may fit better in development than first steps, but before I bother the developers, let me ask the basics? would it introduce any ambiguity if Vector{AbstractFloat} was interpreted as Vector{<:AbstractFloat}. The former seems quite natural, and I have been bitten a few times by inadvertently …

Ambiguity on Vector{<:Abstract*}?

rdeits April 28, 2018, 5:49am 6

It catches a Vector{AbstractFloat}, just like it says:

julia> x = Vector{AbstractFloat}(5)
5-element Array{AbstractFloat,1}:
 #undef
 #undef
 #undef
 #undef
 #undef

julia> f(x)
2

1 Like

Topic		Replies	Views
Why [1, 2, 3] is not a Vector{Number}? New to Julia question , parametric-types	41	7086	December 9, 2022
How does AbstractFloat[1.0f0] work? New to Julia	5	918	January 14, 2021
Vector{Real}, Vector{Float64} MethodError New to Julia	11	2482	July 3, 2019
Union vs. <: AbstractType New to Julia	7	813	December 28, 2020
Is there a good reason why `!(Tuple <: AbstractVector)`? Internals & Design	16	2232	May 4, 2017