Closed ParadaCarleton closed 7 months ago
The lookups very much need to be AbstractArray
:
(ax1=(:x, :y, :z), ax2=(:x, :y, :z))
So we would have to collect
them in format
. (probably should have a better error otherwise). Any reason not to just make them arrays from the start?
This looks like it should work though... I remember even making this work at one point writing it and deciding not to just to keep it simpler:
(:axis1=>[:x, :y, :z], :axis2=>[:x, :y, :z])
Not sure how to weight that up
So we would have to
collect
them informat
. Any reason not to just make them arrays from the start?
No reason for using a tuple, I just keep forgetting whether it's a tuple or an array :sweat_smile: but I assume if this is a problem for me, I'm probably not the only one.
Probably needs a better error catching Tuple and whatever else then.
That would work, but is there a problem with just collect
ing the Tuple?
The problem for me is that if it works, people will use it, and its confusing to see a Tuple
working as an AbstractArray
Some constructors that feel like they should work, but don't ATM:
Can't use pairs either: