ES6 template literals should not use legacy octal strings

test/mjsunit/harmony/templates.js

Index: test/mjsunit/harmony/templates.js
diff --git a/test/mjsunit/harmony/templates.js b/test/mjsunit/harmony/templates.js
index 86caf453a5c998f7cb6f9cabdde145aba400ad2d..90d975ac41c8a7dc1ab190e0380f3fe92ac4f332 100644
--- a/test/mjsunit/harmony/templates.js
+++ b/test/mjsunit/harmony/templates.js
@@ -471,3 +471,16 @@ var obj = {
     // block
   }`jkl`;
 })();
+
+
+(function testLegacyOctal() {
+  assertEquals('\u0000', `\0`);
+  assertEquals('\u00001', `\01`);
+  assertEquals('\u000012', `\012`);

[caitp (gmail), 2014/12/17 18:04:59]

Few other things:

"\0a" matches the grammar `EscapeSequence :: 0 [lookahead ∉ DecimalDigit]`,
while "\012" would be an octal literal.

In SpiderMonkey, they are also throwing when trying to use the legacy octal
literal within a template, so it's probably a good idea to make sure we throw
with message "strict_octal_literal" if we hit an octal literal within a template
span.

+  assertEquals('123', `\123`);
+
+  assertEquals('\\0', String.raw`\0`);
+  assertEquals('\\01', String.raw`\01`);
+  assertEquals('\\012', String.raw`\012`);
+  assertEquals('\\123', String.raw`\123`);
+})();