[Webkit-unassigned] [Bug 143424] New: [ES6] DFG and FTL should be aware of that StringConstructor behavior for symbols becomes different from ToString
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Apr 5 14:49:45 PDT 2015
https://bugs.webkit.org/show_bug.cgi?id=143424
Bug ID: 143424
Summary: [ES6] DFG and FTL should be aware of that
StringConstructor behavior for symbols becomes
different from ToString
Classification: Unclassified
Product: WebKit
Version: 528+ (Nightly build)
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: JavaScriptCore
Assignee: webkit-unassigned at lists.webkit.org
Reporter: utatane.tea at gmail.com
In ES6, StringConstructor behavior becomes different from ToString abstract operations in the spec. (and JSValue::toString).
ToString(symbol) throws a type error.
String(symbol) produces SymbolDescriptiveString(value).
So, in DFG and FTL phase, they should not inline String constructor to ToString.
Now, in the template literals patch, ToString DFG operation is planned to be used for it.
And current ToString behavior is aligned to the spec (and JSValue::toString). I think keeping it is better.
So intead of changing ToString behavior, I think adding StringConstructor operation into DFG and FTL is nice.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150405/147482c3/attachment.html>
More information about the webkit-unassigned
mailing list