142943 2015-03-21 18:51:08 -0700 ES6: Computed Properties should always produce string/symbol keys never numeric indexes 2015-07-27 16:54:50 -0700 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED P2 Normal --- 1 joepeck webkit-unassigned ggaren joepeck ysuzuki oldest_to_newest 1079116 0 joepeck 2015-03-21 18:51:08 -0700 * SUMMARY https://people.mozilla.org/~jorendorff/es6-draft.html#sec-object-initializer-runtime-semantics-evaluation > Runtime Semantics: Evaluation > > ComputedPropertyName : [ AssignmentExpression ] > Let exprValue be the result of evaluating AssignmentExpression. > Let propName be GetValue(exprValue). > ReturnIfAbrupt(propName). > Return ToPropertyKey(propName). > --- > > ToPropertyKey ( argument ) > > The abstract operation ToPropertyKey converts argument to a value that can > be used as a property key by performing the following steps: > > Let key be ToPrimitive(argument, hint String). > ReturnIfAbrupt(key). > If Type(key) is Symbol, then > Return key. > Return ToString(key). * TEST (LayoutTests/js/script-tests/basic-computed-property-name.js) var a = 0; runTest("{[a]: true, get '0'(){ return false; }}[0])") As written, this should actually be `false`, but currently it is `true`. It seems we are treating the index key as an index instead of a string, and it goes down a different path. * NOTES - Firefox behaves correctly here - Chrome does not currently have computed properties 1079118 1 joepeck 2015-03-21 19:29:37 -0700 So it seems "op_put_by_val_direct" is used in lots of places: - computed properties (PropertyListNode::emitBytecode) - array literal with spread (ArrayNode::emitBytecode) - and any put by val used by built-ins The implementation of the op code does special case integer indexes. I'm not sure we can reconcile the difference that only computed properties has with the generic put by value case. It is worth keeping in mind that we will soon have computed getter/setter names, that will also have this same to string conversion of the property. - It seems wasteful to extend the existing opcode because it can be common - It seems wasteful to add a new op code just for this - but it would be easy (just call JSValue::toPropertyKey) I don't see any existing opcodes that would do exactly what we want here without changes. The closest is op_to_index_string (assumes int property provided). 1112596 2 ysuzuki 2015-07-27 16:54:50 -0700 This is now fixed by http://trac.webkit.org/changeset/187464!