When supplied range conflicts with un-shifted index... about tullio.jl HOT 1 OPEN

Every index is in one of two modes: The strict one demands that all match, and the other takes the intersection. The second is applied to any index with a shift.

I'm not sure that's the perfect solution. It means you get an error if you do matrix multiplication and get the sizes wrong, I think it would be pretty surprising to silently take the smallest size there. But when you write x[i+1] - x[i] the obvious behaviour is all values legal for both terms. It could also be a global effect, not per-index.

I also wondered whether explicit ranges should have higher priority, but right now they don't. I guess this is the opposite direction to your complaint, I feel it's a little odd that this disobeys an explicit command:

julia> @tullio a[i] := (1:3)[i+1]   i in 1:5
2-element Vector{Int64}:
 2
 3

from tullio.jl.