You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using StaticArrays.jl often helps avoiding allocation in bottle-neck code. When creating the StaticArray, the length or size must be known to the compiler.
ComponentArrays have this information in its type in its axes. However, currently length and size are based on the underlying array, for which the size might not be known at compile time.
I suggest implementing Base.length for an Axis and use this to implement Base.length and Base.size on getaxes(cv).
The text was updated successfully, but these errors were encountered:
bgctw
added a commit
to bgctw/ComponentArrays.jl
that referenced
this issue
Jun 3, 2022
A maybe-nice feature request.
Using StaticArrays.jl often helps avoiding allocation in bottle-neck code. When creating the StaticArray, the length or size must be known to the compiler.
ComponentArrays have this information in its type in its axes. However, currently length and size are based on the underlying array, for which the size might not be known at compile time.
I suggest implementing Base.length for an Axis and use this to implement
Base.length
andBase.size
ongetaxes(cv)
.The text was updated successfully, but these errors were encountered: