Promise.of(value).then(cb) = cb(value)
promise.then(Promise.of) = promise
My interpretation of these laws for promises is that attaching a callback to
a resolved promise should execute that callback synchronously (though the
callback itself may create an asynchronous promise, introducing
Hi,
In section 15.3.4.3 Function.prototype.apply (thisArg, argArray) (page 119
of Ecma-262, Edition 5.1) there's this note:
'The thisArg value is passed without modification as the this value. This
is a change from Edition 3, where a undefined or null thisArg is replaced
with the global object
On Fri, May 3, 2013 at 1:53 AM, Claus Reinke claus.rei...@talk21.com wrote:
That part I wouldn't be so sure about: in all monads, the .of equivalent
is effect-free (in an IO monad, it does no IO; in a non-determinism
monad, it is deterministic; in a failure/exception monad, it does not
fail;
On May 3, 2013, at 5:33 AM, raul mihaila wrote:
Hi,
In section 15.3.4.3 Function.prototype.apply (thisArg, argArray) (page 119 of
Ecma-262, Edition 5.1) there's this note:
'The thisArg value is passed without modification as the this value. This is
a change from Edition 3, where a
Hi David,
2013/5/2 David Bruant bruan...@gmail.com
IIRC, trying to change the design of harmony:proxies to be able to
represent these (probably started at [1], also motivated by arrays length
property) led to listing invariants (eternal/momentary) and then led to the
idea of a per-proxy
On Wed, May 1, 2013 at 11:59 PM, Kevin Smith wrote:
On Wed, May 1, 2013 at 7:08 PM, Jason Orendorff wrote:
On Wed, May 1, 2013 at 9:18 AM, Kevin Smith wrote:
- Dave, your argument that URI's as a naming mechanism is a failure
cherry-picks cases where URIs were obviously overkill.
What
On Thu, May 2, 2013 at 9:47 AM, Andreas Rossberg rossb...@google.com wrote:
I don't see how logical names can possibly make sense without at least
a rudimentary manager that maps them. Otherwise they are just physical
names.
Yes. A rudimentary way of mapping logical names to URLs is built into
Wait, we've had a misunderstanding somewhere. If you think David's
argument cherry-picks cases, then you must have in mind some cases he
didn't mention that contradict his point. That's what I'm asking for.
I gotcha - that's fair. I concede the point though as not central to my
position.
If we don't expect loaders to treat these names as URLs or respect URL
resolution semantics, then they aren't URLs, and it's bogus to call
them URLs.
I didn't really answer you here.
I think that, considering the fact that module IDs look like URLs, and
effectively perform the same function
9 matches
Mail list logo
