seems useful,
but that’s apparently considered for ES7 or later, anyway.
On Dec 27, 2012, at 5:53 , Brendan Eich bren...@mozilla.com wrote:
Axel Rauschmayer wrote:
http://wiki.ecmascript.org/doku.php?id=strawman:object_model_reformation
Is the object model reformation (OMR) still on the table
On 27 December 2012 05:53, Brendan Eich bren...@mozilla.com wrote:
I have a theory: hashes and lookup tables (arrays or vectors) have
displaced most other data structures because most of the time, for most
programs (horrible generalizations I know), you don't need ordered entries,
or other
Andreas Rossberg wrote:
On 27 December 2012 05:53, Brendan Eich bren...@mozilla.com
mailto:bren...@mozilla.com wrote:
I have a theory: hashes and lookup tables (arrays or vectors) have
displaced most other data structures because most of the time, for
most programs (horrible
http://wiki.ecmascript.org/doku.php?id=strawman:object_model_reformation
Is the object model reformation (OMR) still on the table for ES6?
The reason I’m asking is that I recently remembered a technique from the Java
collections API: you could wrap any collection in a read-only “view
Axel Rauschmayer wrote:
http://wiki.ecmascript.org/doku.php?id=strawman:object_model_reformation
Is the object model reformation (OMR) still on the table for ES6?
It never was -- it missed the cutoff by over five months.
The reason I’m asking is that I recently remembered a technique from
On Jan 1, 2012, at 5:54 AM, Axel Rauschmayer wrote:
http://wiki.ecmascript.org/doku.php?id=strawman:object_model_reformation
Currently, there one can override the built-in operators via elementGet
(getting via []), elementSet (setting via []) and elementDelete (`delete`
operator).
Currently, there one can override the built-in operators via elementGet
(getting via []), elementSet (setting via []) and elementDelete (`delete`
operator). Wouldn’t it make sense to also provide elementIn (`in` operator)?
Probably. It may depend upon how strongly you feel about
http://wiki.ecmascript.org/doku.php?id=strawman:object_model_reformation
Currently, there one can override the built-in operators via elementGet
(getting via []), elementSet (setting via []) and elementDelete (`delete`
operator). Wouldn’t it make sense to also provide elementIn (`in` operator)?
8 matches
Mail list logo