We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e.g. _type_ub(Vector{Vector{T}} where {T<:Int}) == Vector{Vector{Int}}, when the intention is that it is Vector{Vector{T} where {T<:Int}}
The text was updated successfully, but these errors were encountered:
Actually the above comment is incorrect, because Vector{Vector{T} where {T<:Int}} is not a subtype of Vector{Vector{T}}.
Vector{Vector{T} where {T<:Int}}
Vector{Vector{T}}
I'm keeping _type_ub as it is, replacing each typevar with its upper bound. This gives the most general specialisation of the type.
_type_ub
_type_lb is similar, but any typevars which are a parameter of the outermost type are replaces with their lower bound.
_type_lb
e.g. _type_lb(Vector{Vector{T}} where {T<:Int}) == Vector{Vector{Int}} == _type_ub(...) because T is not a parameter of the top type.
_type_lb(Vector{Vector{T}} where {T<:Int}) == Vector{Vector{Int}} == _type_ub(...)
T
e.g. _type_lb(Vector{<:Vector{<:Int}}) == Vector{Union{}} and _type_ub(Vector{<:Vector{<:Int}}) == Vector{Vector{<:Int}}
_type_lb(Vector{<:Vector{<:Int}}) == Vector{Union{}}
_type_ub(Vector{<:Vector{<:Int}}) == Vector{Vector{<:Int}}
Sorry, something went wrong.
No branches or pull requests
e.g. _type_ub(Vector{Vector{T}} where {T<:Int}) == Vector{Vector{Int}}, when the intention is that it is Vector{Vector{T} where {T<:Int}}
The text was updated successfully, but these errors were encountered: