On 5 May 2014, at 20:22, Andrea Giammarchi andrea.giammar...@gmail.com wrote:
@mathias didn't mean to change atob and btoa rather add two extra methods
such encode/decode for strings (could land without problems in the
String.prototype, IMO) with less silly names whatever definition of silly
ES6 additions like Object.assign use [[OwnPropertyKeys]] for getting the
keys of `source` objects. This helps avoid the method gotchas faced by
developers previously with things like `Object.prototype.writable = true`
and `Object.defineProperty(o, 'foo', { value: 'bar' })`.
See
I agree with you that this would be a much better design, but it would break
backwards compatibility with ES5, no?
Minor nitpick: I guess you mean to say that ToPropertyDescriptor should use the
abstract operation HasOwnProperty, not [[HasOwnProperty]]...
Fred
From: John-David Dalton
Allen, Mark and I discussed the [[Origin]] issue and came to the following
consensus:
We remove [[Origin]] and revert to the originally specified behavior (
http://wiki.ecmascript.org/doku.php?id=harmony:proxies_spec) where the
descriptor returned by the proxy is coerced into a fresh, normalized,
I agree with you that this would be a much better design, but it would
break backwards compatibility with ES5, no?
There have been other changes to the spec that are technically back-compat
breaking like Object.keys('x') no longer throwing an error.
I think this change would benefit developers
that does not save you from errors when `Object.prototype.get =
function(){}` since `writable` and `get/set` cannot coexist in a descriptor
... a safe approach is to create `var descriptor = Object.create(null);`
and then set its `value` later on before assignment.
I remember early discussion
iw=say ... is way
On Thu, May 8, 2014 at 2:38 PM, Andrea Giammarchi
andrea.giammar...@gmail.com wrote:
that does not save you from errors when `Object.prototype.get =
function(){}` since `writable` and `get/set` cannot coexist in a descriptor
... a safe approach is to create `var descriptor
OK, hasOwnProperty per descriptor would work too ... probably even easier
as spec change than having all null objects
+1 to that
On Thu, May 8, 2014 at 2:35 PM, John-David Dalton
john.david.dal...@gmail.com wrote:
I agree with you that this would be a much better design, but it would
break
On Thu, May 8, 2014 at 5:23 PM, Tom Van Cutsem tomvc...@gmail.com wrote:
Allen, Mark and I discussed the [[Origin]] issue and came to the following
consensus:
We remove [[Origin]] and revert to the originally specified behavior (
http://wiki.ecmascript.org/doku.php?id=harmony:proxies_spec)
On May 8, 2014, at 1:25 PM, John-David Dalton wrote:
ES6 additions like Object.assign use [[OwnPropertyKeys]] for getting the keys
of `source` objects. This helps avoid the method gotchas faced by developers
previously with things like `Object.prototype.writable = true` and
Thanks for the discussion links, Allen.
I'm I reading it right that there was no concrete resolution to the issue?
- JDD
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
On May 8, 2014, at 4:05 PM, John-David Dalton wrote:
Thanks for the discussion links, Allen.
I'm I reading it right that there was no concrete resolution to the issue?
Right, nothing concrete came out of it so won't happen for ES6.
Post-ES6 is always possible.
Allen
Is Post-ES6 up for discussion? Should I create a spec bug for tracking this?
- JDD
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
On Fri, May 9, 2014 at 1:44 AM, John-David Dalton
john.david.dal...@gmail.com wrote:
Should I create a spec bug for tracking this?
Please do.
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
14 matches
Mail list logo
