Closed GoogleCodeExporter closed 8 years ago
I see why this is useful with numeric indices, but it's also problematic since
it changes the semantics of the indexing operation. To be consistent, the
slicing operation (!!) would have to be changed accordingly, which isn't really
possible with the way arithmetic sequences i..j are defined right now. Last but
not least, indexing is also used with non-numeric indices in Pure (e.g.,
records and dictionaries), so using -k to denote the kth last element of an
aggregate is not always meaningful. Therefore I'm not really convinced that
this is the right thing to do.
I'm setting this to "won't fix" for now, but I invite you to post your patch to
the Pure mailing list so that we can discuss it there.
Original comment by aggraef@gmail.com
on 29 Mar 2011 at 3:14
Original issue reported on code.google.com by
ivxlc...@gmail.com
on 21 Mar 2011 at 12:33