Hey everyone, could someone explain this subtyping behavior to me? It does not seem intuitive to me. Array{T where T} <: AbstractArray{T where T} # true Array{Array{T where T}} <: AbstractArray{Array{T where T}} # also true Array{Array{T where T}} <: AbstractArray{AbstractArray{T where T}} # f…

To elaborate a bit more, if x <: y then in general Point{x} <: Point{y} may not always be true. To begin, your first and second example work because Array <: AbstractArray and what you are passing inside {} are exactly the same i.e. in the second example, you are declaring x = Array{T where T} and…

Unexpected subtyping behavior <:

General Usage

Mattriks November 30, 2019, 8:08pm 2

1 Like

Topic		Replies	Views
Array{T, 1} where T<:Real versus Array{T where T<:Real, 1} General Usage question	5	1177	November 19, 2019
Why does (AbstractArray{Union{Number, T}} where T <: Nothing) != (AbstractArray{Union{Number, Nothing}}) General Usage	1	348	January 11, 2019
Arrays of abstract types within a parametric type Internals & Design type , parametric-types	17	1255	April 21, 2022
SomeType{T} where T:>SomeOtherType General Usage parametric-types	3	1180	December 18, 2017
Subtyping Conventions for Dicts are Unexpected General Usage	7	384	January 6, 2020

Unexpected subtyping behavior <:

Related topics