[Design] Redefining `.low` / `.high` for strided ranges

Hi Chapel Users —

We've been considering a redefinition of .low and .high for strided ranges to have them return the aligned bounds rather than the pure bounds. For example, for the range 1..10 by 2, today, .high would return 10 whereas under the current proposal, it would return 9 (and a different query, .highBound could be used when 10 was desired).

For more details about this proposal and the motivation for it, please refer to Design for querying range low / high bounds in aligned and unaligned ways, including transition · Issue #19836 · chapel-lang/chapel · GitHub. If you have thoughts about it (positive or negative), please comment on the issue or by replying to this message.

Thanks,
-Brad