Skip to content

Conversation

gbrail
Copy link
Collaborator

@gbrail gbrail commented Aug 16, 2024

Generators use a different calling convention and require "activation" in order to pick up the right parameters. This wasn't being triggered unless the generator function had a "yield" statement, resulting in some very strange results. Make sure that it always happens for ES6 generators.

Fixes #1412

Generators use a different calling convention and require "activation"
in order to pick up the right parameters. This wasn't being triggered
unless the generator function had a "yield" statement, resulting in some
very strange results. Make sure that it always happens for ES6
generators.
@p-bakker
Copy link
Collaborator

Think it fixes #1412, not #1413, but otherwise LGTM!

Thnx for looking into it!

@rbri
Copy link
Collaborator

rbri commented Aug 16, 2024

Merge, merge, merge....

@gbrail gbrail merged commit ec45a62 into mozilla:master Aug 17, 2024
3 checks passed
@gbrail gbrail deleted the fix-generator-activation branch August 17, 2024 02:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ES2015 Generators don't work properly in non-interpreted mode
3 participants