Hello,
On 2021-03-16 10:43, Logan Smyth writes:
>> as this code does not seem to take an argument.
>
> The resumption state set by `GeneratorStart` does not take an argument
> because there is no way to access the first resumption value in a
> generator, though there is the `function.sent` propo
Hello,
I am trying to understand how the resuming of execution contexts work.
For instance, step 9 of
https://tc39.es/ecma262/2021/#sec-generatorresume says "Resume the
suspended evaluation of genContext using NormalCompletion(value) as the
result of the operation that suspended it." I can see tha
On 2019-08-17 23:03, Gus Caplan writes:
It's worth noting that engine262 doesn't use the RunJobs
implementation it
has, it uses a separate entrypoint in api.mjs. There is some
work going on
to get rid of RunJobs entirely, as no implementations actually
use it (
https://github.com/tc39/ecma26
Hello Cyril,
On 2019-08-17 21:29, Cyril Auburtin
writes:
You can also have a look at
https://github.com/engine262/engine262, an
interesting way to learn the spec
Thank you for the suggestion. Our goal is to modernize JSExplain
(https://gitlab.inria.fr/star-explain/jsexplain) to be closer
On 2019-08-15 10:53, Alan Schmitt
writes:
Back in ES5.1, there was a specification to evaluate programs
(https://www.ecma-international.org/ecma-262/5.1/index.html#sec-14).
What is the corresponding starting point in the current spec? Is
it
https://tc39.es/ecma262/#sec-scripts ?
Thanks to
Hello,
Back in ES5.1, there was a specification to evaluate programs
(https://www.ecma-international.org/ecma-262/5.1/index.html#sec-14).
What is the corresponding starting point in the current spec? Is
it
https://tc39.es/ecma262/#sec-scripts ?
Best,
Alan
signature.asc
Description: PGP sign
On 2017-02-15 21:54, Alex Vincent writes:
> Ouch. With ES6 and now ES7 released, I am curious as to whether
> someone has a fork out there which implements the recent standards. I
> couldn't find one...
We don't implement the recent standards in JSExplain
(https://github.com/jscert/jsexplain) bu
On 2016-04-13 19:53, Vic9 writes:
> if "{}+{}" is a statement, than how can it return (or yield) a result?
It returns a completion record, like every other construction
(http://www.ecma-international.org/ecma-262/6.0/#sec-completion-record-specification-type).
In most cases you don't get to
On 2015-07-31 06:26, Claude Pache writes:
> The `delete` operator applied to a non-reference just does nothing (no error
> is thrown), whereas an assignment to a non-reference did throw an error.
> I guess that there is some BC risk for trying to turn a non-error into an
> early error, not worth
Hello,
ES6 introduces IsValidSimpleAssignmentTarget to make an early error the
attempt to assign to something that is obviously not a reference. For
instance
#+begin_src javascript
((function () { throw 42 })()) = 3;
#+end_src
is now a syntax error.
Is there a reason why the same does not apply
On 2015-06-20 16:14, Eric B writes:
> The main problem I have with mailing lists is that, unless I'm mistaken, I
> cannot unsubscribe from specific threads. As an example, "The Tragedy of the
> Common Lisp, or, Why Large Languages Explode" is now 33 replies deep and I
> really don't care about it
On 2015-05-19 18:24, Steve Fink writes:
> On 05/19/2015 12:23 AM, Alan Schmitt wrote:
>> On 2015-05-19 06:09, Bergi writes:
>>
>>> Alternatively just use a single equals sign with a parameter list:
>>>
>>> let f(x) = y
>>> let f() = y
>>
On 2015-05-19 06:09, Bergi writes:
> Alternatively just use a single equals sign with a parameter list:
>
> let f(x) = y
> let f() = y
This looks very nice indeed.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
signature.asc
Description: PGP signature
On 2015-04-08 16:59, Allen Wirfs-Brock writes:
> Well, they do for normal loop completions (according to the spec.) but not for
> breaks. I this the latter is a bug. In particular, I think it is pretty
> obvious that:
>eval(“ {0; while (true) {1; break}; 2}”)
> should evaluate to 1
>
> It is
Hi Allen,
On 2015-04-06 02:08, Allen Wirfs-Brock writes:
> Alan,
>
> I freed up a couple minutes for a quick look at this. I want to spend some
> more time look at it deeper as this is an area where I made some fixes just
> a couple weeks ago and I want to review them again to make sure everythi
Hello,
I've been looking into completions records in ES6, and I have a question
regarding loop unrolling, as it seems completion records are dealt with
differently for breaks inside loops and breaks inside blocks.
For while loops, the spec says (this is the part that applies to
a "break" in the s
(Sorry for the latency, but I only get internet access by tethering
here.)
bruan...@gmail.com writes:
> Le 05/08/2013 17:08, Brendan Eich a écrit :
>> Michael Ficarra wrote:
>>> specified that the global object's prototype chain must include
>>> Object.prototype. I am sure there's plenty of code
Hi Michael,
es-disc...@michael.ficarra.me writes:
> Oh, sorry for the duplicate. It appears you guys were just recently
> discussing this, though it failed to turn up in my searches.
The discussion only started on test262. If it's going to entice a spec
change, it's great to talk about it here.
I think
> the spec should explicitly mention this value.
Here is the related bug report for the test262 test that also assumes
this.
https://bugs.ecmascript.org/show_bug.cgi?id=1600
Best regards,
Alan Schmitt
___
es-discuss mailing list
es-discu
Axel Rauschmayer writes:
> Also a function returns a value, does a block evaluate to something?
>
>
> No it doesn’t.
I thought they did evaluate to a "completion type":
http://es5.github.io/#x8.9
One can see this using an Expression statement
(http://es5.github.io/#x12.4) and `eval'. For ins
20 matches
Mail list logo
