I am currently stuck trying to get the benefits of mutable lists while maintaining type covariance logic. Essentially I would like to be able to do the following: abstract VTKData typealias VTKDataGroup{T} Array{T<:VTKData, 1} type VTKUnstructuredData <: VTKData end type VTKStructuredData <: VTKDa…

How important is performance accessing the vectors of “mixed” data? Do the different types have common fields? If the performance of accessing the “blocks” field (which will have to essentially hold pointers to boxed VTKData types) isn’t so important, then the following (using the new syntax) shou…

How to trick Array{T} into behaving covariantly?

General Usage

mohamed82008 June 3, 2017, 12:47pm 8

Ok I think I get it. Real is abstract, but Array{Real} is concrete, which is a nice side effect of non-covariance I guess.

Topic		Replies	Views
Is there a good reason why `!(Tuple <: AbstractVector)`? Internals & Design	16	2232	May 4, 2017
Why? isa([(x,1),(y,1)], Array{Tuple{Stuff,Number},1}) = false General Usage	25	1727	February 23, 2021
Composite Types of Arrays Performance	2	723	May 26, 2018
Ambiguity on Vector{<:Abstract*}? General Usage	11	1306	April 28, 2018
Type signature for nested `AbstractArray` General Usage question	1	493	January 8, 2017

How to trick Array{T} into behaving covariantly?

Related topics