Confirmed users
596
edits
Jetpack/Collections: Difference between revisions
Jump to navigation
Jump to search
→JavaScript Collections: 3 aspects, and motivation
(→Implementation: link bug) |
(→JavaScript Collections: 3 aspects, and motivation) |
||
| Line 3: | Line 3: | ||
= JavaScript Collections = | = JavaScript Collections = | ||
This describes a future module that will have a coherent set of collection/list classes | This describes a future module that will have a coherent set of collection/list classes | ||
This is mostly about 3 aspects: | |||
* A common API for various collection types (array, set, map, OrderedMap etc.), similar to java.util.Collection. | |||
* observers to notify about changes | |||
* operators for whole lists, like concat, merge, substract, intersect etc. | |||
The real value comes from being a coherent API and base functionality that can be used in other APIs, and these other APIs are all fitting together. If each API uses a slightly different API to add/remove items, not only does the programmer have to learn each API, but he also has to do the plumbing between the components all manually. The advantage here is that this is a powerful, yet lean system to plug modules together with custom operators in between. Basically LEGO Technic. | |||
= Functionality = | = Functionality = | ||