ES6 template literals should not use legacy octal strings

test/mjsunit/harmony/templates.js

 // Copyright 2014 the V8 project authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Flags: --harmony-templates --harmony-unicode
 
 var num = 5;
 var str = "str";
 function fn() { return "result"; }
 var obj = {
@@ skipping 453 matching lines @@
 
   {
     // block
   }
   `ghi`;
 
   {
     // 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`);
+})();