Claire Foster

Documenter CI failures should be fixed by #153

> But there's one niggling issue: do you return the range values or the corresponding Axis object Agreed, good question. The reason I didn't do this was because the user...

> At the very least the multi-arg version should be deprecated IMO Perhaps we should do this. I'm a bit cautious about `getproperty` as a general interface because it's kind...

So thinking about the `Base.axes` conundrum, I tried making an `AxisUnitRange` which is returned from `Base.axes(A,i)` for some `A::AxisArray`. It wraps together a combination of `A.axes[i]` and `Base.axes(A.data)[i]` and this...

Thanks Tim, it looks like @mbauman has already done versions of * "turn `Axis` into an `AbstractUnitRange`" (#58) and * "Create a wrapper for both the range and the `Axis`"...

> they basically all need to do this or they can't suport static arrays That's a worry. Is this because of something nasty we're doing in `StaticArrays`, or due to...

Ok thanks a lot, those sound like things which eventually need fixing in Base (to add to the many other places where the immutability of `SArray` breaks assumptions of the...

Some initial work has been done in c1113a3. Needs UI polishing though, since it's not very easy to use.

Hi Nigel, you're quick off the mark! I think there's a few semi-distinct problems to be solved here: - Make a 3D selection UI which is nice to use. My...

By the way, the selection branch is pretty stale. I'll try to rebase it onto master now.