Evaluate how bug-prone the forwarding collections are

[GoogleCodeExporter]

I'm still concerned that our forwarding collections are intensely bug-prone, 
and by analyzing what users really need we might be able to provide something 
more tailored. For example, many users just want to listen to certain events, 
but by having to forward they walk into a minefield.

We should just pick a random sample of users and see how many bugs we find.

Original issue reported on code.google.com by cpov...@google.com on 12 Nov 2013 at 4:58

[GoogleCodeExporter]

(Migrated out from an internal issue filed by kevinb.)

Original comment by cpov...@google.com on 12 Nov 2013 at 4:58

[GoogleCodeExporter]

Of course I totally agree.

One thing that's changed since I initially worried about this:  error-prone.  
We could at least make it an error/warning to, say, override add() without 
addAll().  I bet that 80% of existing users would find themselves broken by 
that. :(

Original comment by kevinb@google.com on 12 Nov 2013 at 6:38

• Changed state: Research
• Added labels: Type-Enhancement

[GoogleCodeExporter]

This issue has been migrated to GitHub.

It can be found at https://github.com/google/guava/issues/<issue id>

Original comment by cgdecker@google.com on 1 Nov 2014 at 4:10

• Added labels: MigratedToGitHub

[GoogleCodeExporter]

Original comment by cgdecker@google.com on 1 Nov 2014 at 4:17

• Changed state: Migrated

[GoogleCodeExporter]

Original comment by cgdecker@google.com on 3 Nov 2014 at 9:08

• Added labels: Restrict-AddIssueComment-Commit