Jishnu Bhattacharya

This goes back to [Tim's upgrade of the axes](https://discourse.julialang.org/t/why-is-there-a-performance-hit-on-broadcasting-with-offsetarrays/32194/4?u=jishnub). Essentially `Base.IdentityUnitRange` is not a lazy wrapper, it only ensures that the axes are the same as the indices it wraps....

To be fair they are not exactly equivalent if the parent does not start at 1. ```julia julia> pairs(OffsetArrays.IdOffsetRange(5:6, 2)) pairs(::OffsetArrays.IdOffsetRange{Int64,UnitRange{Int64}}) with 2 entries: 3 => 7 4 => 8...

Also ```julia julia> hcat(zeros(2, 1:1, 2), zeros(2, 2:3, 2)) ERROR: BoundsError: attempt to access 2×3×2 Array{Float64,3} at index [1:2, 3:4, 1:2] julia> vcat(zeros(1:1, 2, 2), zeros(2:3, 2, 2)) ERROR: BoundsError:...

Perhaps this should be fixed in `Base`?

I agree, this is something that I was thinking of as well. However `Base.cat` appears to ignore indices altogether for arrays hcat(zeros(2, 1:2), ones(2, 10:11)) 2×4 Array{Float64,2}: 0.0 0.0 1.0...

[This](https://github.com/JuliaLang/julia/pull/33890#issuecomment-557717321) might be relevant: > reshaping is essentially an appeal to the linear index representation, and that differs for 1-dimensional objects (for which the linear index can start anywhere) and...

I don't really have an application in mind, this was more about making an offset range and an offset vector behave identically. Currently, we don't have an `OffsetRange

Gentle bump @dlfivefifty (not sure who is maintaining this repo)

Note that with the conversion method now being defined in `OffsetArrays.jl`, the construction of the `DArray` works: ```julia julia> @everywhere using DistributedArrays julia> @everywhere using OffsetArrays julia> r1 = @spawnat...

`dSS[2].m` gets lowered to `getproperty(dSS[2], :m)`, where the first argument is necessarily fetched before evaluation. Perhaps there could be a macro that could evaluate an expression on the host and...