Contact email: bak...@gmail.com
Spec: https://tc39.github.io/proposal-template-literal-revision/
This feature is stage 4 and will be included in the 2018 edition of
ECMA-262.
Summary: ES6 template literals forbid certain escape sequences, like
`\u{not hex}`. But tagged templates expose to user code the raw code points
of the template literal, and some applications only care about those. As
such, this stage 4 TC39 proposal allows such invalid escape sequences in
tagged template literals. The "cooked" value of such a template (that is to
say, with escape sequences interpreted), which is also exposed to user
code, is `undefined`.
Interop risk: This new language feature allows syntax that was previously a
SyntaxError, so compatibility risk is low.
Firefox has shipped this feature (
https://bugzilla.mozilla.org/show_bug.cgi?id=1317375 ).
Safari has implemented this feature (
https://bugs.webkit.org/show_bug.cgi?id=166871 ) and shipped it in at least
Tech Preview.
Edge has not implemented this feature (
https://github.com/Microsoft/ChakraCore/issues/2344 ).
Tracking bug: https://bugs.chromium.org/p/v8/issues/detail?id=5546
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
