[PIVOT-1045] Refactor read-only classes to use a common abstract class to reduce code

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: core-collections
• Assignee: Roger Lee Whitcomb
• Reporter: Roger Lee Whitcomb
• Created: 12/Aug/19 21:13
• Updated: 12/Aug/19 23:14

Description

All of the "read-only" collection classes (such as ArrayAdapter, EnumList, ImmutableList) share the concept that "add", "insert", "remove", etc. all throw exceptions because they are unsupported in a read-only collection. It would reduce code and expose the common functionality if they were all implemented on top of a single abstract class that provides a uniform implementation of these unsupported methods.

I propose to implement a ReadOnlySequence class that does this and refactor all other existing places (at least) with the common subclass.