Re: Shorthand for "function" keyword

For all new syntax proposals or discussions, I recommend writing a Babylon plugin + Babel transform to prove that it's even possible before presenting it for feedback. Rick On Tue, Nov 14, 2017 at 8:26 AM Isiah Meadows wrote: > Also, most decent text editors, including

Re: Native Proxy Syntax

Inline... On Wed, Aug 23, 2017 at 11:08 AM Vihan Bhargava wrote: > The `Proxy` class is great for classes however at the moment, the current > syntax can be unwieldy: > > ``` > class MyClass { >constructor() { >return new Proxy(this, { >get:

Re: Oddities in 2017-07-25 meeting notes?

Additionally, if you enjoy your meeting notes in a rendered-markdown form, with less oddities and mistakes (but certainly not zero), these are maintained by TC39: http://tc39.github.io/tc39-notes/ Rick On Mon, Aug 7, 2017 at 5:28 PM Rick Waldron <waldron.r...@gmail.com> wrote: > lo

Re: Oddities in 2017-07-25 meeting notes?

lol, that's especially amusing since Jaswanth Sreeram has not attended a meeting since 2014. On Sat, Aug 5, 2017 at 2:49 AM Jordan Harband wrote: > I don't see that in the original ( > https://github.com/rwaldron/tc39-notes/blob/master/es8/2017-07/jul-25.md#10ii-vision-thing >

Re: nits on BigInt Proposal

Inline On Fri, Aug 4, 2017 at 10:52 AM kai zhu wrote: > looking at the use-cases for this feature @ > https://github.com/tc39/proposal-bigint#use-cases, i'm not convinced it > improves everyday programming, or outweigh the benefit and simplicity > having a single number

Re: Re: Strict (non-coercing) expressions

On Sat, Apr 15, 2017 at 7:02 AM Bruno Jouhier wrote: > I don't know the ins and outs of the "nobody likes", I'll just respond as > a "language user". > The committee, which is now comprised of more practitioners/language users than runtime implementors and academics

Re: Proposal of Multithread JavaScript

Just to make sure this gets attention... Lars Hansen's Shared Memory and Atomics proposal is at stage 2: - https://github.com/tc39/ecmascript_sharedmem - https://github.com/rwaldron/tc39-notes/blob/master/es7/2016-07/jul-28.md#10iia-shared-memory-and-atomics -

Re: expanding comments proposal

Overloading comments is not likely to be accepted as a new feature; doing so could be dramatically "web breaking". You may be interested in this: https://github.com/rwaldron/tc39-notes/blob/master/es6/2014-09/sept-25.md#types Rick On Thu, Oct 20, 2016 at 1:14 PM Gert Cuykens

Re: Power operator, why does -2**3 throws?

Here's some more specific notes: On Fri, Oct 14, 2016 at 7:31 AM Cyril Auburtin wrote: > I would expect `-2**3` to return -8, or `-2**2 == -4`, since it should be > like `-(2**3)` > Math.pow(-2, 3) === -8 Math.pow(-2, 2) === 4 To get -4: -Math.pow(-2, 2) > Firefox

Re: Power operator, why does -2**3 throws?

On Fri, Oct 14, 2016 at 7:31 AM Cyril Auburtin wrote: > I would expect `-2**3` to return -8, or `-2**2 == -4`, since it should be > like `-(2**3)` > This was discussed extensively during the design process and determined that requiring user code to be explicit about

Re: Making Object Literals a sub-class of Object

On Fri, Oct 14, 2016 at 9:05 AM Brian Ninni wrote: > I did a quick search and didn't find any recent mentions of this topic. > > On more than one occasion I've had to determine whether something was a > plain old Object, or some other class. This involves checking that the

Re: Proposal: add an option to omit prototype of objects created by JSON.parse()

var o = JSON.parse('{}'); Object.setPrototypeOf(o, null); Rick On Thu, Sep 29, 2016 at 9:30 PM Danielle McLean wrote: > From: Olivier Lalonde (mailto:olalo...@gmail.com) > Date: 30 September 2016 at 07:21:10 > > > Given that JSON.parse doesn't necessarily return an

September 28, 2016 Meeting Notes

# Sept 28 2016 Meeting Notes Brian Terlson (BT), Michael Ficarra (MF), Jordan Harband (JHD), Waldemar Horwat (WH), Tim Disney (TD), Michael Saboff (MS), Chip Morningstar (CM), Daniel Ehrenberg (DE), Leo Balter (LB), Yehuda Katz (YK), Jafar Husain (JH), Domenic Denicola (DD), Rick Waldron (RW

September 29, 2016 Meeting Notes

), Rick Waldron (RW), John Buchanan (JB), Kevin Gibbons (KG), Peter Jensen (PJ), Tom Care (TC), Dave Herman (DH), Bradley Farias (BF), Dean Tribble (DT), Jeff Morrison (JM), Sebastian Markbåge (SM), Saam Barati (SB), Kris Gray (KGY), John-David Dalton (JDD), Daniel Rosenwasser (DRR), Jean-Francis Paradis

September 27, 2016 Meeting Notes

), Rick Waldron (RW), John Buchanan (JB), Kevin Gibbons (KG), Peter Jensen (PJ), Tom Care (TC), Dave Herman (DH), Bradley Farias (BF), Dean Tribble (DT), Jeff Morrison (JM), Sebastian Markbåge (SM), Saam Barati (SB), Kris Gray (KGY), John-David Dalton (JDD), Daniel Rosenwasser (DRR), Mikeal Rogers (MRS

Re: Support () => {}() syntax?

On Thu, Sep 29, 2016 at 3:14 PM Michał Wadas wrote: > Similar proposal is already here, do expressions. > Additionally... > > On 30 Sep 2016 12:06 a.m., "Olivier Lalonde" wrote: > >> I occasionally write IIFE to avoid introducing `let` variables,

Re: Syntax Proposal: Anonymous Arguments

What does this mean: let f = @; On Fri, Sep 23, 2016 at 4:32 PM Jordan Harband wrote: > @ is currently reserved for decorators, # currently for private fields. > There aren't a lot of compelling syntax options left, to be sure. > > On Fri, Sep 23, 2016 at 11:35 AM,

Re: Proposal: `if-else` and `switch` as expressions

In addition to Cait's recommendation, I'd suggest proving out the grammar before presenting a proposal. Babel provides mechanisms for defining experimental syntax extensions, which can then be used as evidence to support proposal discussion. It's very important to remember that syntax additions

Re: es7-membrane: A new ECMAScript 2016 Membrane implementation

More importantly, Ben Newman is championing a proposal for nested imports: https://github.com/tc39/ecma262/pull/646 - Rick On Tue, Aug 23, 2016 at 11:30 PM /#!/JoePea wrote: > Sidenote: Ben Newman's [Reify](https://github.com/benjamn/reify) > implements experimental deferred

Re: Why ES6 introduced classes yet `Symbol` not to be used with `new`?

All of the recorded discussion can be found here: - https://github.com/rwaldron/tc39-notes/blob/master/es6/2013-03/mar-14.md#46-symbols - https://github.com/rwaldron/tc39-notes/blob/master/es6/2013-09/sept-18.md#44-symbols On Mon, Aug 15, 2016 at 4:29 AM Andrea Giammarchi <

July 27 2016 Meeting Notes

(IS), John Neumann (JN), Domenic Denicola (DD), Rick Waldron (RW), Stefan Penner (SP), Jonathan Sampson (JS), Caridy Patiño (CP), Sam Tobin-Hochstadt (STH), John Buchanan (JB), Kevin Gibbons (KG), Lars Hansen (LHN), Peter Jensen (PJ), Tom Care (TC), Dave Herman (DH), Bradley Farias (BF), Kris Gray

July 28 2016 Meeting Notes

(IS), John Neumann (JN), Domenic Denicola (DD), Rick Waldron (RW), Stefan Penner (SP), Jonathan Sampson (JS), Caridy Patiño (CP), Sam Tobin-Hochstadt (STH), John Buchanan (JB), Kevin Gibbons (KG), Lars Hansen (LHN), Tom Care (TC), Dave Herman (DH), Bradley Farias (BF), Kris Gray (KSG), Adam Klein (AK

July 26 2016 Meeting Notes

(IS), John Neumann (JN), Domenic Denicola (DD), Rick Waldron (RW), Stefan Penner (SP), Jonathan Sampson (JS), Caridy Patiño (CP), Sam Tobin-Hochstadt (STH), John Buchanan (JB), Kevin Gibbons (KG), Lars Hansen (LHN), Peter Jensen (PJ), Tom Care (TC), Dave Herman (DH), Bradley Farias (BF), Kris Gray (KSG

Re: Reason for strange ExponentiationExpression & UpdateExpression productions?

gt; as an argument for update in the prefix case? > > Not a critical question, but I am very curious. > > Thanks, > Bradford > > On Thu, Jul 21, 2016 at 12:26 PM Rick Waldron <waldron.r...@gmail.com> > wrote: > >> Bradford, >> >> Take a look at the tests th

Re: Reason for strange ExponentiationExpression & UpdateExpression productions?

Bradford, Take a look at the tests that I wrote for that syntax, I think they will be helpful in understand what that syntax actually is: https://github.com/tc39/test262/blob/master/test/language/expressions/exponentiation/exp-operator-precedence-unary-expression-semantics.js#L34-L66 Rick On

Re: ES7 - the standard

Adding to Andreas response, all proposals are developed in public and tracked from here: https://github.com/tc39/proposals Rick On Mon, Jun 20, 2016 at 5:19 AM Andreas Rossberg wrote: > Async functions are coming along fine and are on track for ES8. There has > been little

Re: AND and OR in if statement

This is a non-starter, as AND and OR are already valid identifiers. On Tue, May 24, 2016 at 9:15 PM Francis Clavette wrote: > Hi, > I’d like to be able to use AND for && and OR for || in conditional > statements in a future version of ECMAScript. It’s a feature I’ve

Re: Re: Tracking proposals should be standardized with issues

Clarification: Bocoup is not a member of Ecma. Leo, Yehuda and I are representatives for jQuery Foundation, which is a member. Rick On Wed, May 11, 2016 at 10:12 PM Domenic Denicola wrote: > From: es-discuss [mailto:es-discuss-boun...@mozilla.org] On Behalf Of G. > Kay Lee > >

Re: meeting notes for march 2016?

Where are they? I haven't seen anyone post them for approval. On Tue, Apr 5, 2016 at 8:39 PM Jordan Harband wrote: > The notes were taken, but have not yet been approved and posted on > https://github.com/rwaldron/tc39-notes . > > On Tue, Apr 5, 2016 at 11:22 AM,

Re: monadic extension to do-notation

What does this do? let finalPromise = do { let a; a <- b; } Currently, that's an expression that means "a less than negated b" Rick On Sun, Feb 7, 2016 at 12:07 PM Raphael Mu wrote: > The ES Promise is an instance of Monad, a property that implies a much > more

January 26th 2016 Meeting Notes

), Ian Halliday (IH), Keith Miller (KM), Tim Disney (TD), Misko Hevery (MH), Brad Green (BG), Kevin Smith (KS), Brad Nelson (BN), JF Bastien (JFB), Shu-yu Guo (SYG), Rick Waldron (RW), Staś Małolepszy (STM), Dean Tribble (DT) ## Agenda https://github.com/tc39/agendas/blob/master/2016/01.md

January 28th 2016 Meeting Notes

Disney (TD), Misko Hevery (MH), Brad Green (BG), Kevin Smith (KS), Brad Nelson (BN), JF Bastien (JFB), Shu-yu Guo (SYG), Rick Waldron (RW), Staś Małolepszy (STM), Dean Tribble (DT) ## Agenda https://github.com/tc39/agendas/blob/master/2016/01.md ## Function#toString && Function#isPort

January 27th 2016 Meeting Notes

Miller (KM), Tim Disney (TD), Misko Hevery (MH), Brad Green (BG), Kevin Smith (KS), Brad Nelson (BN), JF Bastien (JFB), Shu-yu Guo (SYG), Rick Waldron (RW), Staś Małolepszy (STM), Dean Tribble (DT) ## Agenda https://github.com/tc39/agendas/blob/master/2016/01.md ## FastTrack AWB: slide (Ecma

Re: Additional methods for Objects (like Arrays)

On Fri, Jan 29, 2016 at 6:08 PM Kaustubh Karkare wrote: > I have recently come to feel the need for Object.map, which is like > Array.map, > except that it receive keys instead of indices. > > Object.prototype.map = function(mapFn, context) { > return

Re: Propose simpler string constant

On Wed, Dec 16, 2015 at 6:20 AM Thomas wrote: > IMHO it'd be a huge mistake to not use symbols for enums. > > In my head this: > > const colours = enum { > Red, > Yellow, > Green, > Blue > } > > should 'desugar' to something like this in ES6: > > const

Re: Propose simpler string constant

On Thu, Dec 17, 2015 at 3:33 PM Steve Kinney wrote: > I did some initial thinking about this and looked at Rust and Swift as > prior art. I started something similar to what was being discussed but came > across some edge cases as I went along. > >

Re: The "Pipeline" Operator - Making multiple function calls look great

Has anyone tried writing grammar for this? The "|>" token requires a a lookahead to disambiguate the bit wise OR operator `|` - Rick On Sun, Dec 6, 2015 at 6:38 PM Gilbert B Garza wrote: > > It doesn’t look like there is any redeeming quality about this change, > it

Re: Concise Method Binding

On Mon, Nov 9, 2015 at 8:45 PM JD Isaacks wrote: > Considering the proposals for both concise methods and the bind operator I > think it would be a great addition to be able to use them together. > > I am already seeing a lot of this: > > class Foo { > bar = () => { > //

Re: Generator getter method

On Tue, Nov 10, 2015 at 2:28 PM Mohsen Azimi wrote: > > for (let corner of rectangle.getCorners()) { > console.log(corner); > } > ``` > > for (let corner of rectangle.corners) { > console.log(corner); > } > ``` > > Which seems cleaner > Either could've been called "corners"

Re: Concise Method Binding

On Tue, Nov 10, 2015 at 6:59 PM Isiah Meadows wrote: > It's using an ES7 proposal, and it's a method bound to the instance. > Ah, right—that proposal does not have consensus:

Re: Decorators for functions

Or just use call constructor: class F { #decorator call constructor() { ... } } Rick On Tue, Oct 20, 2015 at 9:19 AM Matthew Robb wrote: > Why not just do: > > ``` > const {myFunc} = { > @someDecorator; > myFunc() { > > } > }; > ``` > > > - Matthew Robb > > On

Re: Exporting Symbols

On Fri, Oct 16, 2015 at 2:47 PM Dean Landolt wrote: > The symbol registry is a great way to map universal (not just global, but > fully cross-realm) names (strings) to unique, distinct concepts (symbols). > But as a flat string namespace has all the same kinds of issues

Re: Exporting Symbols

The math.trunc part is completely irrelevant, leftover from fiddling around—sorry for the noise! On Thu, Oct 15, 2015 at 4:13 PM Rick Waldron <waldron.r...@gmail.com> wrote: > Symbol has built-in API for making Symbols available across all code > realms: > > http://www.ecma

Re: Exporting Symbols

Symbol has built-in API for making Symbols available across all code realms: http://www.ecma-international.org/ecma-262/6.0/#sec-symbol.for http://www.ecma-international.org/ecma-262/6.0/#sec-symbol.keyfor You can create a generated key and export it, giving your consumers only the key, which

Re: Re: Additional Math functions

On Mon, Oct 5, 2015 at 2:58 PM Marius Gundersen wrote: > Wouldn't it make sense to wait for the bind syntax [1] before introducing > new methods that work on arrays? > The functions don't accept arrays or operate on arrays—they accept any number of arguments (eg.

Re: Re: Additional Math functions

On Thu, Oct 1, 2015 at 6:52 PM Eli Perelman wrote: > Reviving this thread, doing any type of simple statistics is more verbose > than it probably needs to be as calculating sums, averages, etc. makes most > resort to Array reduction. I understand the need for methods such

Re: Exponentiation operator precedence

Thanks again to Brendan for taking time to write this up. And to Mark, thanks for reviewing this and expeditiously providing valuable feedback—it's greatly appreciated. Rick On Thu, Sep 24, 2015 at 8:27 AM Mark S. Miller wrote: > I won't try to guess where the rendering

Re: Global lexical tier

On Tue, Sep 1, 2015 at 10:41 PM SaamBarati1 wrote: > Hi Allen, > > What were the requirements for the global lexical scope? Is it written > somewhere I can read? I came up empty after a quick search of > esdiscuss.org. > > I think the whole point of ES6 lexical scoping is

Re: Exponentiation operator precedence

On Tue, Aug 25, 2015 at 11:12 AM Mark S. Miller erig...@google.com wrote: I think we should drop the feature. Given the conflict between * the history of ** in other languages, * the general pattern that unary binds tighter than binary any solution at this point will confuse many people.

July 28 2015 Meeting Notes

(TC), John Neumann (JN), Dave Herman (DH), Brendan Eich (BE), Rick Waldron (RW), Mike Pennisi (MP) ## Introduction BT: (logistics) AWB: I will chair until John N. arrives. ## Adoption of Agenda AWB: https://github.com/tc39/agendas/blob/master/2015/07.md YK: Propose that future agendas

July 30 2015 Meeting Notes

(TC), John Neumann (JN), Dave Herman (DH), Brendan Eich (BE), Daniel Ehrenberg (DE), Dan Gohman (DG), Andreas Rossberg (ARB), Rick Waldron (RW), Mike Pennisi (MP), Akrosh Gandhi (AG), Jonathan Sampson (JS) ## 7 Test262 Updates (Brian Terlson, Mike Pennisi) [Slides]( https

July 29 2015 Meeting Notes

(TC), John Neumann (JN), Dave Herman (DH), Brendan Eich (BE), Daniel Ehrenberg (DE), Dan Gohman (DG), Andreas Rossberg (ARB), Rick Waldron (RW), Mike Pennisi (MP), Akrosh Gandhi (AG), Jonathan Sampson (JS) ## 6.11 The scope of use strict with respect to destructuring in parameter lists

Re: for statement with index and value

On Wed, Jul 15, 2015 at 2:21 AM Sebastian Zartner sebastianzart...@gmail.com wrote: That only works if all values are distinct. The following will result in the wrong index for the last item: Indeed, but useful if the program can reliably know that the array will contain only unique entries.

Re: for statement with index and value

If you need the _index of_ a value in an array, there is always... indexOf ;) for (let value of values) { let index = values.indexOf(value); } Rick On Tue, Jul 14, 2015 at 4:16 PM Tab Atkins Jr. jackalm...@gmail.com wrote: On Mon, Jul 13, 2015 at 7:13 PM, Tingan Ho tinga...@gmail.com wrote:

Re: insteadof operator

It's not immediately clear which `path` binding `insteadof` will resolve to here: import path from path; function dirOp(path) { with (path) { if ((insteadof path).dirname(path) === /) { // ... } } } dirOp({ path: }); Or even... import path from path;

Re: Move es-discuss to discuss.webplatform.org?

On Fri, Jun 19, 2015 at 5:12 PM C. Scott Ananian ecmascr...@cscott.net wrote: No, thank you.​ Email clients are the ultimate forum aggregators. I'm with Scott. Regardless, this conversation is a non-starter. Rick ___ es-discuss mailing list

Re: revive let blocks

On Thu, Jun 18, 2015 at 9:54 AM Boris Zbarsky bzbar...@mit.edu wrote: On 6/18/15 9:01 AM, Kyle Simpson wrote: In addition to the fact that this feature is long since co-existing in FF and doesn't seem to have broken the web Firefox doesn't ship let support on the web by default yet. For

Re: revive let blocks

On Thu, Jun 18, 2015 at 12:55 PM Boris Zbarsky bzbar...@mit.edu wrote: On 6/18/15 11:30 AM, Rick Waldron wrote: Strange, this works in the console, but not in a script https://i.gyazo.com/e55d26495c3fe8b01938fe1b99664682.png Yep, it's entirely possible the console opts in to let. It also

Re: Providing object iterators beyond just Object.keys()

, 2015 at 11:05 AM, Rick Waldron waldron.r...@gmail.com wrote: Silence because it wasn't a priority, relative to finishing ES6. It's not forgotten and still on track for ES7 development. Rick On Tue, May 26, 2015 at 11:59 AM Gijs Kruitbosch gijskruitbo...@gmail.com wrote: Perhaps surprisingly

Re: Providing object iterators beyond just Object.keys()

Silence because it wasn't a priority, relative to finishing ES6. It's not forgotten and still on track for ES7 development. Rick On Tue, May 26, 2015 at 11:59 AM Gijs Kruitbosch gijskruitbo...@gmail.com wrote: Perhaps surprisingly, I had actually asked around and looked through recent threads.

Re: Non-binding destructuring assignment

On Wed, Apr 29, 2015 at 12:54 PM Tab Atkins Jr. jackalm...@gmail.com wrote: On Wed, Apr 29, 2015 at 4:39 AM, Elie Rotenberg e...@rotenberg.io wrote: Using array destructuring assignment and constraining linting rules, I often find myself having to chose names for bindings I don't intent on

Re: super.prop assignment can silently overwrite non-writable properties

On Mon, Apr 20, 2015 at 2:31 PM Allen Wirfs-Brock al...@wirfs-brock.com wrote: On Apr 20, 2015, at 11:11 AM, Rick Waldron wrote: On Mon, Apr 20, 2015 at 1:45 PM Allen Wirfs-Brock al...@wirfs-brock.com wrote: On Apr 20, 2015, at 9:38 AM, Jason Orendorff wrote: We're implementing `super

Re: Array comprehensions with Spread operator

On Wed, Apr 15, 2015 at 2:27 PM Mark S. Miller erig...@google.com wrote: Dave Herman did an excellent presentation at one of the TC39 meetings that convinced us all to drop comprehension syntax from ES6. I remember it surprised us all including, earlier Dave, which led to his presentation.

Re: generator function requirements

On Sun, Apr 12, 2015 at 11:59 AM Mark Volkmann r.mark.volkm...@gmail.com wrote: I couldn't find this in spec. Is it required for generator functions to return an object that is both iterable (has Symbol.iterator method) and an iterator (has next method). It seems Babel does this, but I want

Re: generator function requirements

://people.mozilla.org/~jorendorff/es6-draft.html#sec-generator-objects Rick On Sun, Apr 12, 2015 at 6:53 PM, Rick Waldron waldron.r...@gmail.com wrote: On Sun, Apr 12, 2015 at 11:59 AM Mark Volkmann r.mark.volkm...@gmail.com wrote: I couldn't find this in spec. Is it required for generator

Re: Unicode normalization problem

On Wed, Apr 1, 2015 at 2:59 PM monolithed monolit...@gmail.com wrote: ```js var text = 'ЙйЁё'; text.split(''); // [И, ̆, и, ̆, Е, ̈, е, ̈] ``` Possible solutions: 1. ```js text.normalize().split('') // [Й, й, Ё, ё] ``` I like it, but is no so comfortable 2. ```js

Re: Extending object literal property value shorthand

Inline... On Wed, Mar 25, 2015 at 12:25 AM Bob Myers r...@gol.com wrote: Thanks Rick. Yes, I had been hoping to make the following work: x = {a: 1}; y = {b: 2}; z = {x.a, b.y}; // {a: 1, b: 2} This is not destructuring per se. Of course, and that's not what I was exploring in attempting

Re: Iterating default function arguments

On Wed, Mar 25, 2015 at 2:40 AM Robin Cafolla ro...@zombiemongoose.com wrote: Hi there, I was wondering if there were any plans to modify `arguments` to include default parameters (e.g. changing it from a simpleParameterList) or to include a new property that does allow iteration of all

Re: Object arithmetic--operator alternative to Object.assign

On Tue, Mar 24, 2015 at 7:09 PM Edwin Reynoso eor...@gmail.com wrote: For different objects this is the only way I see possible with destructuring. IMO it's a bit ugly and weird to read deep destructuring: ``` let x = { a: 1 }; let y = { b: 2 }; let { x: { a }, y: { b } } = { x, y }; ```

Re: Supporting feature tests directly

On Sun, Mar 22, 2015 at 4:47 PM Getify Solutions get...@gmail.com wrote: So why not just add a sandbox, and ... means to catch error Other than the `import` / `export` thing I mentioned, for the exact reason why `eval(..)` and `new Function(..)` are not preferred (which roughly do the same

Re: Single destructuring argument to an arrow function

Inline... On Thu, Mar 19, 2015 at 4:50 PM Jan-Ivar Bruaroey j...@mozilla.com wrote: Hi group! First post, so be gentle. Welcome I love how arrow functions allow single arguments to be passed without parenthesis, so I expected this to work: Promise.all([true, false]).then([foo, bar]

Re: Class double-bind

On Thu, Mar 5, 2015 at 1:40 PM Luke Scott l...@cywh.com wrote: On Mar 5, 2015, at 9:20 AM, Kevin Smith zenpars...@gmail.com wrote: However, the double-binding issue makes this weirder. If non-const-class declarations were like non-const-function declarations, where there is only one binding

Re: How to fix the `class` keyword

On Wed, Mar 4, 2015 at 8:03 AM Benjamin (Inglor) Gruenbaum ing...@gmail.com wrote: Did you seriously just plug your blog post in es-discuss? Yes, and this is not the first time: https://mail.mozilla.org/pipermail/es-discuss/2013-June/031589.html Rick

Re: Function name property

On Sun, Mar 1, 2015 at 4:17 AM Leon Arnott leonarn...@gmail.com wrote: On Sun, Mar 1, 2015 at 3:28 AM, Allen Wirfs-Brock al...@wirfs-brock.com wrote: If you want both a TCP-able from and a local (most closely enclosing callable thing) form then the later should also presumably also be

Re: Function name property

On Thu Feb 26 2015 at 8:22:55 PM Claude Pache claude.pa...@gmail.com wrote: Le 27 févr. 2015 à 02:04, Allen Wirfs-Brock al...@wirfs-brock.com a écrit : On Feb 26, 2015, at 3:55 PM, Mark S. Miller wrote: For most of these, my first reaction is meh. They all make sense and violate no

Re: Object.assign and inherited properties

On Fri Feb 27 2015 at 5:31:51 PM Andri Möll an...@dot.ee wrote: `Object.assign` has **nothing to do with inheritance**, that's what I am saying, not just supporting. What is my personal position here is that `Object.assign` is the wrong method/tool/function to do anything prototypal or

Re: `new Set()` or `new Map()` with more than one argument

On Tue Feb 24 2015 at 10:48:59 AM Allen Wirfs-Brock al...@wirfs-brock.com wrote: On Feb 24, 2015, at 5:52 AM, Axel Rauschmayer wrote: I’ve accidentally created the wrong set a few times: ```js let set = new Set('red', 'green', 'blue'); // WRONG: same as new Set(['r', 'e', 'd'])

Re: `new Set()` or `new Map()` with more than one argument

On Tue Feb 24 2015 at 12:22:25 PM Mark S. Miller erig...@google.com wrote: As always with proposals to extend arity -- even if reserved by a thrown error in a previous release -- how would you feature test for the extended functionality? I suspect the awkwardness of feature testing is one of

Re: Why is export default var a = 1; invalid syntax?

On Wed Feb 18 2015 at 4:40:34 PM Jesse McCarthy es-discuss-2015...@jessemccarthy.net wrote: Jesse, you can do: `export default class Foo extends Backbone {}` Ok, thanks. The empty block is required? Yes, just like: function Foo() {} Where the braces are the syntactic boundary around

Rev10 Ecma-402 Draft now available

PDFs and .doc file available at: http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts - Technical Changes - https://bugs.ecmascript.org/show_bug.cgi?id=3804 Bug 3804 - Implement NewTarget and subclassing semantics - https://bugs.ecmascript.org/show_bug.cgi?id=3803 Bug

Rev9 Ecma-402 Draft now available

PDFs and .doc file available at http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts - 6.2.1: Definition of Unicode Locale Extension Sequences incorrect https://bugs.ecmascript.org/show_bug.cgi?id=Bug 1244 - 12.1.1.1 ToDateTimeOptions: Change Throw parameter to true

January 29 2015 Meeting Notes

Morningstar (CM), Adam Klein (AK), Igor Minar (IM), Misko Hevery (MH), Istvan Sebastyan (IS), Rick Waldron (RW), Ben Newman (BN), Yehuda Katz (YK) Not present? Peter Jensen (PJ), Dmitry Lomov (DL), Sam Tobin-Hochstadt (STH), Mark Miller (MM), Brendan Eich (BE), PLEASE UPDATE THE PARTICIPANTS LIST

January 28 2015 Meeting Notes

# January 28 2015 Meeting Notes Brian Terlson (BT), Jonathan Turner (JT), Allen Wirfs-Brock (AWB), John Neumann (JN), Rick Waldron (RW), Jeff Morrison (JM), Erik Arvidsson (EA), Peter Jensen (PJ), Yehuda Katz (YK), Dave Herman (DH), Waldemar Horwat (WH), Dmitry Lomov (DL), Domenic Denicola (DD

January 27 2015 Meeting Notes

# January 27 2015 Meeting Notes Brian Terlson (BT), Jonathan Turner (JT), Jordan Harband (JHD), Allen Wirfs-Brock (AWB), John Neumann (JN), Rick Waldron (RW), Eric Ferraiuolo (EF), Jeff Morrison (JM), Sebastian Markbage (SM), Erik Arvidsson (EA), Peter Jensen (PJ), Yehuda Katz (YK), Dave Herman

Re: JavaScript 2015?

On Thu Jan 22 2015 at 9:58:24 PM Allen Wirfs-Brock al...@wirfs-brock.com wrote: On Jan 22, 2015, at 5:40 PM, Brendan Eich wrote: Domenic Denicola wrote: I believe the cutover was decided in the September 25 meeting. I must have missed it if so -- do the notes record it?

Re: @@toStringTag spoofing for null and undefined

On Wed Jan 21 2015 at 4:11:04 PM Mark Miller erig...@gmail.com wrote: On Wed, Jan 21, 2015 at 1:05 PM, Jordan Harband ljh...@gmail.com wrote: Just checking: Are we talking about adding it to each instance as a non-configurable non-writable data property? Mark: No, not to each instance, but

Re: (x) = {foo: bar}

On Tue Jan 06 2015 at 4:53:05 PM Isiah Meadows impinb...@gmail.com wrote: Okay: is this a valid statement/expression? I didn't think so, but I may be wrong. ```js ({ foo(); bar(); }) ``` That's not valid for any grammar in up to and including ES6. To make it valid, pick one, but not both:

Re: (x) = {foo: bar}

On Tue Jan 06 2015 at 2:18:47 AM Isiah Meadows impinb...@gmail.com wrote: From: Alex Kocharin a...@kocharin.ru To: Gary Guo nbdd0...@hotmail.com, bren...@mozilla.org bren...@mozilla.org Cc: es-discuss@mozilla.org es-discuss@mozilla.org Date: Tue, 06 Jan 2015 06:59:52 +0300 Subject:

Re: Implicit coercion of Symbols

On Sat Jan 03 2015 at 3:56:38 PM Brendan Eich bren...@mozilla.org wrote: Axel Rauschmayer wrote: On 03 Jan 2015, at 19:52, Brendan Eich bren...@mozilla.org mailto:bren...@mozilla.org wrote: None of the objects in the examples bz cited are Arrays -- what did you mean? When I though

Re: Implicit coercion of Symbols

On Sat Jan 03 2015 at 5:56:33 PM Brendan Eich bren...@mozilla.org wrote: Rick Waldron wrote: Subjectively: I think it's nice in theory, but bad in practice. Compared to what? Converting a symbol to asilent-but-deadly string? Sorry, that was poorly delivered—I was editorializing

Re: Implicit coercion of Symbols

On Sat Jan 03 2015 at 6:30:43 PM Andrea Giammarchi andrea.giammar...@gmail.com wrote: Agreed with Brendan, and I've thought the same. It's been also years we have problems using unknonw objects in the wild, i.e. ```js var n = {__proto__:null}; var s = String(n); // error, No default

Re: Implicit coercion of Symbols

On Sat Jan 03 2015 at 8:25:40 PM Brendan Eich bren...@mozilla.org wrote: Rick Waldron wrote: That example above is pretty compelling for throw always consistency. With a new Reflect.* API for converting a symbol to its diagnostic/debugging string? If you agree, please file

Re: Implicit coercion of Symbols

On Sat Jan 03 2015 at 9:41:57 PM Alex Kocharin a...@kocharin.ru wrote: Also, if you want to prevent mistakes like `object['blah' + symbol]`, linters could be changed to forbid/warn about concatenation inside property names. How would a linter know that `symbol` was actually a Symbol? Rick

Re: Can `let`, `static` and `yield` still be used as Identifier?

On Thu Jan 01 2015 at 9:47:47 PM Gary Guo nbdd0...@hotmail.com wrote: It seems that in JSFiddle running on Firefox, let declaration is disabled. So this cannot explain. I don't know why you'd say that, considering the fiddle works just fine. Open your developer console and you'll see the

Re: Implicit coercion of Symbols

On Fri Jan 02 2015 at 7:53:22 PM Brendan Eich bren...@mozilla.org wrote: Caitlin Potter wrote: One reason it might make sense to throw, is people converting values to string names for use as object properties. Reason you'd want to throw would be to prevent accidentally making the key

Implicit coercion of Symbols

Kyle Simpson brought this up on Twitter today and I think it deserves one last look. Here's an example of the issue: var sym = Symbol(description); sym + ; // Throws Meanwhile... var sym = Symbol(description); String(sym); // Symbol(description) * (* appears to be the convention that

Re: Can `let`, `static` and `yield` still be used as Identifier?

On Wed Dec 31 2014 at 2:45:57 PM Alex Kocharin a...@kocharin.ru wrote: Firefox does parse `let=1` as illegal, Under what circumstance? All of these function according to the spec: let = 1; console.log(let); // 1 var let = 1; console.log(let); // 1 let let = 1; // SyntaxError

Re: classes and enumerability

Inline On Tue Dec 23 2014 at 10:24:06 PM Brendan Eich bren...@mozilla.org wrote: It ain't over till it's over. If we can't tweak ES6 to fix a mistake, just because process, then we're doing it wrong. OTOH the bar for any change, including what is regarded by many (but not all) as a fix, is

Re: classes and enumerability

On Wed Dec 24 2014 at 4:49:36 PM Kevin Smith zenpars...@gmail.com wrote: Here is the summary: Total Files Read: 11038 Files Containing Explicit 'enumerable: false': 149 Occurrences of 'enumerable: false' (and variants): 206 I love this kind of analysis - thanks! I was actually inspired

Re: classes and enumerability

To be clear, the only conclusion to be drawn from my exercise was that there isn't a broad pain being felt by all developers all the time, going out of their way to explicitly define non-enumerable properties. My motivation always begins at: how to evolve the language based on the most common

  1   2   3   4   5   6   7   8   9   10   >