Reference ECMAScript 11.0 specifically (#821)

[Relequestual]

Fixes #821
Reference specific version of emca262.

[ssilverman]

I’d like to encourage a better PR title.

[awwright]

@ssilverman Good suggestion
@Relequestual I also added a # to your PR description to make it a link

[awwright]

I'm not sure if this is in the scope of this PR, but as I noted in #821, we also need to be specific about the flags the RegExp is built with: The u flag changes how backslash escapes work, but is necessary for Unicode support.

[Relequestual]

I'm not sure if this is in the scope of this PR, but as I noted in #821, we also need to be specific about the flags the RegExp is built with: The u flag changes how backslash escapes work, but is necessary for Unicode support.

Sure, makes sense to me. I'll make a change.

[Relequestual]

@awwright I've pushed a new commit which notes that regular expression SHOULD be built with support for unicode as per defined in ECMA 262.

If you approve of this change, we can merge this!

[Relequestual]

The above commit mess is brought to you by "Using caps in your branch names!"
Never do that =]

[ssilverman]

Change the PR title to reference "11th edition" instead of the 10th.

[karenetheridge]

The commit message also references 10 (presumably a rebase and rewording will be done after all reviewing is complete?)

[Relequestual]

The commit message also references 10 (presumably a rebase and rewording will be done after all reviewing is complete?)

I guess so, but I don't usually. But OK.

[Relequestual]

Given the unicode issue is now resolved. I'll consider this OK to merge once automated checks are complete.