Confirmed users
13
edits
Jetpack/Collections: Difference between revisions
Jump to navigation
Jump to search
Shamelessly renamed into "JavaScript Collections" + added design constraints (clean + documentation)
(Leveraging WeakMap should be considered) |
(Shamelessly renamed into "JavaScript Collections" + added design constraints (clean + documentation)) |
||
| Line 1: | Line 1: | ||
Author: Ben Bucksch | Author: Ben Bucksch | ||
= Collections = | = JavaScript Collections = | ||
This describes a future module that will have a coherent set of collection/list classes, with a common API, similar to java.util.Collection. | This describes a future module that will have a coherent set of collection/list classes, with a common API, similar to java.util.Collection. | ||
= | = Functionalities = | ||
* Base API implemented by all collections | * Base API implemented by all collections | ||
| Line 31: | Line 31: | ||
* Other classes | * Other classes | ||
** Pretty much anything that takes a list in Jetpack could be using this API, at least optionally. | ** Pretty much anything that takes a list in Jetpack could be using this API, at least optionally. | ||
= Design = | |||
The implementation will be clean code that doesn't add any properties to the JavaSript types' prototypes. | |||
The code will be documented using the [http://code.google.com/intl/en/closure/compiler/docs/js-for-compiler.html JSDoc conventions]. | |||
= Example = | = Example = | ||