andralex wrote:
We need to improve ranges instead of using opApply for such
trivial
iteration patterns. Apologies that the thread didn't make this
clear.
Will close this now - sorry.
Thanks for taking the time to process my pull request. I'd argue
that we could keep the "opApply fix" until ranges are improved,
but at the same time, keeping things (arguably) "broken" may
motivate for improvement more :)
That said, given the whole "return by value" thing for closed
containers, and the fact that "front" can't be forwarded a
operators, I'm curious to known just _HOW_ ranges *could* ever be
improved to support the current scenario.
I'll drop the issue here regardless, but I will admit that I
don't see how any solution other than opApply could ever work...
