StaticArrays.jl
StaticArrays.jl copied to clipboard
export SUnitRange
I feel like SUnitRange is useful enough (especially for slicing other StaticArrays) to merit exporting.
Yes, this isn't unreasonable... :)
There has been a long-standing plan to support static ranges, LinearIndices and CartesianIndices with StaticArrays. These things would be returned by axes and indices. I've been waiting for v1.0 for that to happen (because compatibility is hard enough between v0.6 users and v1.0 users already) so it might be time to have a rethink of this soon.
Sure, if it's a question of API stability/not committing to this exact form for fewer "breaking" changes once more general ranges are worked out I'm happy to keep manually importing this secret functionality.
OK thanks. Please bump this again soon-ish if I don't get to this.
This PR addresses #620. It would be nice to have a docstring though, perhaps with an example in use, and the docs should also mention this.
Friendly bump --- could this be merged please?
What's the status of this PR? Is this just waiting for resolving the conflicts?
Friendly ping; please reconsider this PR. If anything else needs to be done I am willing to do it or make another PR if that is preferred.
I think the only problem with SUnitRange is https://github.com/JuliaArrays/StaticArrays.jl/issues/978. It would be better to have SUnitRange <: AbstractUnitRange, but changing the supertype may be a breaking change because the type is widely used, I guess.
Considering SUnitRange as a stable API is not a bad practice, so exporting it would be okay for me.