Where's the grief, exactly? The fact that these objects are showing up in heap dumps does not imply performance impact, and no performance impact was claimed, nor were any measurements provided. To state that iterators "have to be garbage collected" is misleading; the Java garbage collector traces live objects, never looking at garbage, which means that ephemeral garbage is virtually free. You also have to consider JVM optimizations like scalar replacement, which is basically an approximation of stack allocation. Gary also makes a good point about how replacing iteration with index access on a List can backfire depending on the underlying implementation of List.
On Fri, Nov 23, 2018 at 12:20 AM Oleg Kalnichevski <[email protected]> wrote: > > I am _strongly_ against it. Last time you did that it had caused us a > lot of grief. > > https://issues.apache.org/jira/browse/HTTPCORE-361 > > Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
