-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Add values and indices virtual properties to IdOffsetRange #316
Comments
One issue is the difference between julia> values(a)
IdOffsetRange(values=5:8, indices=5:8)
julia> a.values
5:8 |
As i understand, the displayed form is meant to act as a constructor, and not to indicate properties. Are there other array types where property access corresponds to the displayed form? |
The default display for a struct type is to present a constructor syntax given it's fields. julia> struct Foo
x::Int
y::Int
end
julia> Foo(3,2)
Foo(3, 2) The constructor itself appears like it was generated by julia> Base.@kwdef struct MyIdOffsetRange
values::UnitRange
indices::UnitRange
end
MyIdOffsetRange
julia> MyIdOffsetRange(values=5:8, indices=5:8)
MyIdOffsetRange(5:8, 5:8) If the default display were as follows, I would understand more clearly that the fields correspond to the displayed arguments. julia> Base.show(io::IO, r::IdOffsetRange) = print(io, IdOffsetRange, "(", r.parent, ", ", r.offset, ")")
julia> a = OffsetArrays.IdOffsetRange(1:4, 4)
IdOffsetRange(1:4, 4) However, a deliberate choice was made to display the keyword form. It's frustrating that one cannot extract the |
Currently when you show an
IdOffsetRange
it displaysindices
andvalues
:The intuition from this display is that an
IdOffsetRange
might have avalues
andindices
property. However, this is not the case.I suggest that we add those properties based on what is shown via
show
:OffsetArrays.jl/src/axes.jl
Line 278 in 08dc371
An example implementation is as follows.
The text was updated successfully, but these errors were encountered: