| Summary: | Computed Name in Async Method | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Kanguk Lee <p51lee> |
| Component: | JavaScriptCore | Assignee: | Ross Kirsling <ross.kirsling> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | mark.lam, webkit-bug-importer, ysuzuki |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Local Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
I've found more cases below:
let x = { 0 : x => { } , } ; // x["0"].name is "" but "0" is expected.
Pull request: https://github.com/WebKit/WebKit/pull/6913 Committed 257114@main (c99e9b77dcb6): <https://commits.webkit.org/257114@main> Reviewed commits have been landed. Closing PR #6913 and removing active labels. |
// input.js class x { async [ "f" ] ( ) { } } print(x.prototype.f.name); _____________________ Hello, Executing the input.js using JSC prints "async", but "f" is expected. Running the input.js with JSC results in: --- $ jsc input.js async --- while other engines behave like: --- # V8 (used console.log) $ node input.js f # GraalJS $ js input.js f --- WebKit version: 615.1.10