Some suggestions and questions about `JuxtArray` about juxta.jl HOT 2 OPEN

Also not sure it it makes sense but could make it

struct JuxtArray{...} <: AbstractArray

so it behaves like a regular array. Might make sense if it's meant to be accessed like ja[4, 5, 1], etc.

from juxta.jl.

Why make the struct mutable?

It is mutable because the sel!/ isel! methods use getindex to create a new array and assign them to the JuxtArray.array field. This can be solved by using view instead of getindex or by forcing sel!/isel! to create new JuxtArrays. I am more inclined towards the second option in agreement with issue #7.

I'm wondering if it would be better to use Symbols instead of Strings as the key.

Absolutely. The keyword arguments in sel! and isel! would be cleaner as well if we use symbols. Thank you for the link to the explanation of symbols. I was reluctant to use them mainly because I did not understand their purpose. That link was helpful.

I used to use @Assert but apparently in C/C++, Python, and Julia they seem more for checking developer mistakes and may actually be disabled by certain optimization levels. So might be better to throw exceptions or something else.

Oh, I did not know that. Thank you. Will do.

from juxta.jl.