Closed GoogleCodeExporter closed 8 years ago
another option: just rename it to something else, like forArrayRange or
forArrayIndex
people currently using it will get an compile error and will have to check the
documentation how to adapt their code.
Original comment by heroldsi...@googlemail.com
on 27 Oct 2009 at 1:06
You're right, that is an option... just one that leaves an undesirable end
state of
the method having a weird name. (Iterators.forSubarray()?)
Either we do that, or I'm leaning toward just removing it. Users do have the
workaround of Arrays.asList().subList().iterator().....
Original comment by kevin...@gmail.com
on 29 Oct 2009 at 7:02
Definitely going to remove it. I discovered that the vast majority of our
internal
users are using it like "Iterators.forArray(a, 0, a.length)"... thus deriving
negative
value from the presence of this overload.
Original comment by kevin...@gmail.com
on 3 Nov 2009 at 6:32
Original comment by kevin...@gmail.com
on 5 Nov 2009 at 1:11
Original issue reported on code.google.com by
kevin...@gmail.com
on 23 Oct 2009 at 7:08