It's just that ranges are so attractive in the way they
"lazily" fetch values that it would make it easier to wrap
associative arrays in struct that return relevant ranges based
on the aa's content of constructing the result, than returning
the range/or result.
Typos, read:
It's just that ranges are so attractive in the
way they "lazily" fetch values that it would make it easier to
wrap associative arrays in struct that return relevant ranges
based on the aa's content INSTEAD of constructing the result, THEN
returning a range/or said result (which implies the decision of
what structure holds the result, rather than just delegating this
part to the person using the struct).
