I have a question related to collections in general.
I have the impression that ES4 will someday accept some kind of high-level
concurrency, possibly Erlang-style. If so, we will probably need the ability to
perform some kind of (destructive) pattern-matching/switch-type on the contents
of a
The current definition in 1.2.2 of what Map(o) does is a harmful dead end. The
current behavior is:
- If o is already a Map then leave it alone.
- Otherwise enumerate the visible properties of o and construct a Map out of
those.
This is harmful because it's guaranteed to cause current and
Last call for comments. Minor changes since previous drafts (and some
comments at the beginning to address changes that are known to come).
--lars
Title: The class "Map"
The class Map
NAME: "The class 'Map'"
FILE: spec/library/Map.html
