2013/4/1 Jeff Walden jwalden...@mit.edu
Note that this could also be construed as a feature, in certain cases.
The dead object proxy Mozilla has, previously mentioned here (can't find
a link), has all its traps throw an error with a message saying Dead
object. If the trap returns
Should this be added to test-262?
It'd be cool if test-262 took pull requests :).
From: es-discuss-boun...@mozilla.org [mailto:es-discuss-boun...@mozilla.org] On
Behalf Of Yusuke SUZUKI
Sent: Monday, April 1, 2013 22:44
To: Allen Wirfs-Brock
Cc: es-discuss@mozilla.org
Subject: Re: RegExp Flags
+1
Additionally I propose to give more JS friendly method names:
Intersection as `and`:
set1and2 = set1.and(set2);
Union as `or`:
set1or2 = set1.or(set2);
Complement as `not`:
set1butNot2 = set1.not(set2);
Peter Michaux wrote:
On Mon, Mar 4, 2013 at 10:56 AM, Tab Atkins Jr.
Is there any collected reference to what's been accepted from Object
Literal Extensions [1]? There's definitely out of date stuff on there
and I'm not sure what things have been formally accepted (with
consensus) for ES6, which are generally assumed to be accepted for ES6,
and which are
It's all in the specification draft.
http://people.mozilla.org/~jorendorff/es6-draft.html#sec-11.1.5
http://people.mozilla.org/~jorendorff/es6-draft.html#sec-13.3
In general, read the spec. draft not the wiki pages which are neither complete,
accurate, or normative.
allen
On Apr 2, 2013,
On 4/2/2013 10:40 AM, Allen Wirfs-Brock wrote:
It's all in the specification draft.
http://people.mozilla.org/~jorendorff/es6-draft.html#sec-11.1.5
http://people.mozilla.org/%7Ejorendorff/es6-draft.html#sec-11.1.5
http://people.mozilla.org/~jorendorff/es6-draft.html#sec-13.3
On 4/1/2013 10:24 PM, Kenneth Russell wrote:
On Sun, Mar 31, 2013 at 1:42 PM, Kevin Gadd kevin.g...@gmail.com wrote:
One could also argue that people using typed arrays to alias and munge
individual values should be using DataView instead. If it performs poorly,
that can hopefully be addressed
It;s moved and morphed:
http://people.mozilla.org/~jorendorff/es6-draft.html#sec-11.1.8
Got it - thanks!
{ Kevin }
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
Le 02/04/2013 04:24, Kenneth Russell a écrit :
Agreed. DataView's methods are all simple and should be easy to
optimize. Because they include a conditional byte swap, they can't run
quite as fast as the typed arrays' accessors -- but they shouldn't
need to. DataView was designed to support file
On Tue, Apr 2, 2013 at 3:03 PM, Aymeric Vitte vitteayme...@gmail.com wrote:
Le 02/04/2013 04:24, Kenneth Russell a écrit :
Agreed. DataView's methods are all simple and should be easy to
optimize. Because they include a conditional byte swap, they can't run
quite as fast as the typed arrays'
Is there a reason why DataView wasn't specified as static methods that take
an ArrayBuffer in the first place? That would solve the problem of figuring
out when/how often to create DataView instances, and eliminate the garbage
created by using DataViews.
On Tue, Apr 2, 2013 at 3:23 PM, Kenneth
On 04/02/2013 12:13 AM, Tom Van Cutsem wrote:
The true/false return protocol doesn't prevent exceptions to be thrown from
the trap. It's perfectly fine for the dead object proxy's preventExtensions
trap to throw an object is dead exception. In fact, that's precisely what
would happen if one
Yes: API consistency. An ArrayBuffer is opaque; to work with the data
it contains, instantiate a view.
On Tue, Apr 2, 2013 at 3:36 PM, Kevin Gadd kevin.g...@gmail.com wrote:
Is there a reason why DataView wasn't specified as static methods that take
an ArrayBuffer in the first place? That
On 4/1/13 at 5:40 AM, sa...@ccs.neu.edu (Sam Tobin-Hochstadt) wrote:
Using `.dispose()` is manual management of the allocation and
deallocation of object. Manual memory management is fundamentally
non-modular -- you can't encapsulate it in a library, and it requires
describing memory management
An important distinction here - and one I think Bill and Brendan and others
have gotten at some, and I've been trying to get at - is that weak
references (and similar concepts, like weak maps and weak event listeners)
unfortunately encompass a set of different problems and end up being used
to
15 matches
Mail list logo
