RFR 8169808 Stream returning methods should specify if they are late binding (original) (raw)
Martin Buchholz martinrb at google.com
Wed Nov 23 01:21:40 UTC 2016
- Previous message: RFR 8169808 Stream returning methods should specify if they are late binding
- Next message: RFR 8169808 Stream returning methods should specify if they are late binding
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Nov 22, 2016 at 4:24 PM, Martin Buchholz <martinrb at google.com> wrote:
On Mon, Nov 21, 2016 at 1:06 PM, Paul Sandoz <paul.sandoz at oracle.com> wrote:
See the SpliteratorLateBindingFailFastTest. That could be refactored out as it’s conflating two concepts and is too collection/map focused. I took a look at that test, and saw that ArrayDeque doesn't get tested there because it's less predictable at throwing CME. ArrayDeque expends fewer resources on catching concurrent modification than classes with a modCount, and that's my own preference as well.
- Previous message: RFR 8169808 Stream returning methods should specify if they are late binding
- Next message: RFR 8169808 Stream returning methods should specify if they are late binding
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]