Repository files navigation

The AbstractArray interface in Base Julia is still relatively young.The purpose of this library is to solidify extensions to the currentAbstractArray interface, which are put to use in package ecosystems likeDifferentialEquations.jl. Since these libraries are live, this package willserve as a staging ground for ideas before they are merged into Base Julia. For thisreason, no functionality is exported so that if such functions are addedand exported in a future Base Julia, there will be no issues with the upgrade.

• JuliaLang/julia#22216
• JuliaLang/julia#22218
• JuliaLang/julia#22622
• JuliaLang/julia#25760
• JuliaLang/julia#25107

The following common array types are being understood and tested as part of thisdevelopment.

• Array
• Various versions of sparse arrays
• SArray
• MArray
• FieldVector
• ArrayPartition
• VectorOfArray
• DistributedArrays
• GPUArrays (CLArrays and CuArrays)
• AFArrays
• MultiScaleArrays
• LabelledArrays

If one is looking for an interface which includes functionality for statically-computed values, seeStaticArrayInterface.jl.This was separated from ArrayInterface.jl because it includes a lot of functionality that does not give substantive improvementsto the interface, and is likely to be deprecated in the near future as the compiler matures to automate a lot of its optimizations.

7.0: Setup to use the new v1.9 package extensions. All static interface functions were moved toStaticArrayInterface.jl. All packagesusing one of the subpackages (ArrayInterfaceCore, ArrayInterfaceStaticArrays, etc.) shouldupdate to v7 by simply depending on ArrayInterface.jl, unless static interface functionswere used in which case a dependency on StaticArrayInterface.jl is also necessary.

6.0: ArrayInterface.jl completely removed all usage of Requires.jl and conditional dependenciesdue to compile time impact. All of the Requires.jl support changed to subpackages within therepository which are registered in the General registry. These subpackages are required byany packages which seek to use the additional functionality.

2.0: Changed the default ofismutable(array::AbstractArray) = true. We previously defaulted toBase.@pure ismutable(array::AbstractArray) = typeof(array).mutable, but there are a lot of caseswhere this tends to not work out in a way one would expect. For example, if you put a normal arrayinto an immutable struct that adds more information to it, this is considered immutable, even ifall of thesetindex! methods work (by forwarding to the mutable array). Thus, it seems safer to justalways assume mutability is standard for an array, and allow arrays to opt-out.