Kevin Gibbons

We should figure out if we want to use html entities for non-ASCII stuff, and enforce that decision. Currently we use both `«` and `«`.

Editors discussed this briefly and were only really in favor of moving DefineMethodProperty.

Yeah, there should be a lint rule for this. (I prefer a lint rule to outright rejecting these inputs because it's nicer to get _some_ output while iterating.)

Firefox issue is https://bugzilla.mozilla.org/show_bug.cgi?id=1739648. Still nightly-only, though.

Looks like Chrome is also shipping in Canary. All three major engines now have this shipping in their nightly builds. [Chrome platform status](https://chromestatus.com/feature/5714791975878656) says this is expected to go out...

My preference would be to use the %SymbolSpecies% notation and move the well-known symbols table to immediately following the intrinsics table. That way we reduce the total number of novel...

See also #385.

[figure-2.png](https://github.com/tc39/ecma262/blob/7acacc524213058a2368b5fa751fac7ea08ba230/img/figure-2.png) also needs to be updated, since it contains the text `@@hasInstance`.

Also would be good to have a NOTE near the symbol table mentioning the old notation, I think.

I think it's easier if we don't try to make them into intrinsics. Apart from being primitives, they also do not have different identities across realms. They're really a different...