I have a use case for `Object.getOwnPropertyDescriptors` – it may or may
not be to your liking, but I have one. I'm currently implementing a library
to help with employing more pure functional programming techniques in
JavaScript environments. This includes such things as (mostly) forcing
, which I *think* is pretty much what I'm
trying to say as well, albeit I'm doing a poorer job at it.
-- Marcus
On Mon, Apr 7, 2014 at 10:42 PM, Allen Wirfs-Brock al...@wirfs-brock.comwrote:
On Apr 7, 2014, at 12:06 PM, Marcus Stade wrote:
Thanks Allen! When reading the issue, I can't quite make
which was the
original issue that motivated the currently spec'ed behavior.
On Apr 7, 2014, at 3:30 AM, Marcus Stade wrote:
Thanks for filing that! Now I also know where to file bugs, so doubly
thanks!
-- Marcus
On Mon, Apr 7, 2014 at 10:00 AM, David Bruant bruan...@gmail.com wrote
In section 25.1.2 of the
spechttp://wiki.ecmascript.org/lib/exe/fetch.php?id=harmony%3Aspecification_draftscache=cachemedia=harmony:working_draft_ecma-262_edition_6_04-05-14.pdfit
says:
The function returns an object that conforms to the IteratorResult
interface. If a previous call to the next
Does this mean that the body of a generator function is strict mode, or
just that yield is reserved?
-- Marcus
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
Could the iterator protocol be extended to also have a `current` or `prev`
property, which contains the result of the previous call to `next`? If
`next` has never been called, presumably this property would return
`undefined`.
I've searched the archives for this question, and the only
On Sun, Mar 23, 2014 at 7:37 PM, David Bruant bruan...@gmail.com wrote:
Any old object. It's a structural or duck-typed protocol.
I see, this was the bit of insight I was missing. Thanks!
-- Marcus
___
es-discuss mailing list
es-discuss@mozilla.org
7 matches
Mail list logo
