Mathieu Hofman

The repl should not be able to observe non observable behavior. Dev tools may show implementation details that reveal what would be unobservable to the program. My understanding is that...

> It most definitely can! E.g. it's reasonable for devtools to observe the values of dead variables, even though dead variables are otherwise unobservable. Sorry I was originally only thinking...

> The iterator is returning a value, which may throw when we try to coerce into a native promise. In principle I'd say yes, but this will complicate things quite...

But only if `closeIteratorOnRejection` and not `done`, right ?

PTAL @bakkot @jridgewell . I decided to ignore the operation type when closing the iterator and solely rely on the `done` value. If the sync iterator decides it isn't actually...

@bakkot @jridgewell, PTAL I believe this now specifies the behavior we discussed in https://github.com/tc39/ecma262/pull/2600#discussion_r772716388 > We could consider rejecting with `TypeError` for missing `throw` like `yield *`. This is yet...

As discussed in plenary, I've updated the PR to throw a TypeError on missing "throw". cc @codehag I'll try to whip up some test262 cases for these changes.

> EDIT: Scrap this, the iterator record gets rewrapped later This confusion shows we need a way to make the current behavior of internal only more clear. > EDIT EDIT:...

Yeah my plan is to write some tests, but I'll create an issue on test262 now.

Wondering if it'd complicate definitions to refer to things like `console.log` as a bound method? When you consider Node.js where you can create multiple `Console` instances, `log` is clearly a...