On Tue Sep 20 03:38 PM, Bob Myers wrote:
>
> People in the real world continue to wonder why they can't
> pick/destructure from objects into objects, instead of just variables.
>
> http://stackoverflow.com/questions/39602360/es6-destructuring-reassign
> ment-of-object?noredirect=1#39602360
On Thu Oct 22 07:44 AM, Andreas Rossberg wrote:
> > determined at creation time, allowing for massive engine optimization,
>
Ya I'm not sure from which hat "massive engine optimization" comes from?
What's meant is likely using decorators as annotations (compile time
optimizations hints):
On Tue Oct 20 05:30 AM, Axel Rauschmayer wrote:
> The decorator proposal does not include decorators for functions,
> because it isn’t
> clear how to make them work in the face of hoisting.
>
What's the obsession with decorators?
Decorators are like saying everyone can decorate their Christmas
On Tue Jul 14 10:43 AM, Andreas Rossberg wrote:
https://mail.mozilla.org/pipermail/es-discuss/2015-June/043307.html
https://mail.mozilla.org/pipermail/es-discuss/2015-June/043307.html
Complexity is very much a psychological aspect. And random
special cases, syntactic additions, and
On Mon Jul 13 10:22 PM, Kevin Smith wrote:
Destructuring is here to help:
for (let [index, value] of [1, 2, 3].entries())
console.log(index + : + value)
The entries method returns an iterator of [index, value] pairs.
Can't there be a 'key iterator' syntax?
for (let
On Tue Jul 14 09:27 AM, Domenic Denicola wrote:
From: es-discuss [mailto:es-discuss-boun...@mozilla.org] On Behalf Of
Matthew
Robb
Why not use the new meta syntax?
If I thought this was a real problem that
needed solving,
Disagree
As early as the mid-1980’s, it was observed that
On Fri Jun 26 05:23 PM, Brian Terlson wrote:
https://github.com/tc39/tc39-notes/blob/master/es6/2015-05/may-29.md
Yay to Value types
and +1 for the per-realm thinking
For typeof, this would seem intuitive:
var ColorType1 = ValueType(Symbol(Color), {...});
var ColorType2 =
On Tue Jun 30 09:55 AM, Andreas Rossberg wrote:
typeof ColorType1 // Color:s1 // where s1...sN is a generated
increment/key for a new user symbol
typeof ColorType2 // Color:s2
typeof ColorType3 // Other:s3
typeof ColorType4 // s4
A seemingly predictable name is a
On Fri Apr 24 01:35 AM, James Burke wrote:
If not natively supported in ES, it would be great to get a pointer to
the officially blessed transform of an ES module body to something
that can be bundled. Something that preserves the behaviors of the
mutable slots, and allows using the
Not so pretty but:
import * as global from “@global”;
Or some bindings:
import {Promise} from “@global”;
From: es-discuss [mailto:es-discuss-boun...@mozilla.org] On Behalf Of Mark
Miller
Sent: April 17, 2015 11:53 AM
To: Glen Huang
Cc: Mark S. Miller; es-discuss@mozilla.org
Subject: Re:
What's the history of the unused keyword package, is it from Java?
Been thinking about this lately, could an external module be called a package?
package/file.js
package something {
export class foo {}
}
package other {
export class foo {}
export module bar {
export class foo {}
On Fri Apr 11 05:52 PM, Domenic Denicola wrote:
What use cases does this solve for JavaScript, not TypeScript?
Not sure, benefit comes down to subjective preference. Keeps the single
'module' per file pattern from node.js
Is it safe to use the 'package' keyword then, no proposals for using
On Sun Feb 9 07:30 PM, Brendan Eich wrote:
Jonathan Bond-Caron wrote:
Thoughts on adding options/flags
Just say no.
http://ariya.ofilabs.com/2011/08/hall-of-api-shame-boolean-trap.html
This is a symptom. We are resisting the larger issue of do both or
design-by-
committee unioning
On Fri Feb 7 12:14 PM, Tab Atkins Jr. wrote:
From a user perspective, can someone explain what chain() does?
.chain returns what is directly inside the promise, without doing any
additional
magic. This is different from .then, which flattens
promises.
For a more concrete example,
On Fri Feb 7 06:50 AM, Anne van Kesteren wrote:
On Fri, Feb 7, 2014 at 12:45 PM, Yutaka Hirano yhir...@chromium.org wrote:
Sorry for knowing little about ES consensus, is this the final decision?
Will you change it again?
Yeah, some clarity would be nice.
From a user perspective, can
On Fri Oct 25 11:48 PM, Ilya Grigorik wrote:
On Fri, Oct 25, 2013 at 6:24 AM, Jonathan Bond-Caron jbo...@gdesolutions.com
mailto:jbo...@gdesolutions.com wrote:
I disagree, if you want to treat this as an optimization problem,
let's look at it:
1. x number of resources/files
On Sun Oct 27 09:35 AM, François REMY wrote:
± How would you suggest to deliver an application over internet (e.g.
± myapp.zip)? Isn't that a bundle already?
This claim is bogus. In all the cases I know, the packages are unzipped by
the OS
before running the application, and the
On Thu Oct 10 02:22 PM, David Bruant wrote:
Among other benefits [1]:
pushed resources are cached individually by the browser and can be reused
across many pages
= It's not clear this can happen with an asset.zip
Opposite benefit of using assets.zip, only a single cache entry to lookup.
About Generic Bundling in:
https://github.com/rwaldron/tc39-notes/blob/master/es6/2013-09/modules.pdf
script src=assets.zip$/lib/main.js/script
It could be reworked as:
link rel=loader type=application/zip href=assets.zip
script src=lib/main.js/script
Simple pattern for packaging web apps
On Tue Jun 25 09:34 AM, Kevin Smith wrote:
import classes/foo; // use default namespace
new foo.bar();
module ns from classes/foo ; // alternative namespace
new ns.bar();
How is the first example any better than the second? The first is far
more
I've been experimenting with the modules definition and find it unfortunate
there's no default literal name for a module.
Could there be an optional 'namespace' or literal name within the module block?
module classes/foo {
namespace foo;
export class bar {}
}
import classes/foo; //
The loader hooks are fantastic. In the case of translate(), consider:
module Button from classes/ui/Button.js
module Button from classes/ui/Button.dart
module Button from classes/ui/Button.ts
module Button from classes/ui/Button.coffee
module Button from classes/ui/Button.zip
module Button
22 matches
Mail list logo
