Kevin Gibbons

@jmdyck Just to make sure we're all on the same page: editor group agrees that the existing labels aren't great, but we didn't like the suggestions here and we couldn't...

> `InitializeReferencedBinding` also calls `ReturnIfAbrupt` on its 2 parameters, so it might make sense to include it in this PR. Done. In the process I marked initialization of `let x;`...

> Probably the toggle should append a query string snippet that gets preserved Alternative is to put it in localStorage, so it's also preserved when you come back to it....

Sure, that works. Makes the state machine a little complicated, though, because you don't want navigating to such a URL to set the persistent bit. What I'm thinking is: -...

@gibson042 That's a slightly different thing - search results would probably go in sessionStorage, like we do for [the references pane](https://github.com/tc39/ecmarkup/blob/1db79a9dde9b163056d186fd254dbd81070dead3/js/multipage.js#L63-L115). So go ahead and open a different issue I...

If we decide they should be universally included, sure.

I only remembered that we were vaguely in support of it, not that we necessarily intended to actually change it. But if we did, sure, sounds good.

The issue there isn't about the macro, it's the fact that there's no evaluation order for the arguments defined, and when they're abstract operations they can have side effects which...

> In algorithm steps, all aliases should be introduced using Let or with a parameter list before they are used. There are other ways we introduce aliases. Other than those...

Also, the things which are currently `console.log` warnings should become linting errors, ideally. Edit: done in https://github.com/tc39/ecmarkup/pull/229.