15959 2007-11-12 13:32:32 -0800 JSObject needs getToNumber to avoid costly string/number conversions 2012-09-06 17:33:05 -0700 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) Mac OS X 10.4 RESOLVED INVALID P2 Normal --- 1 eric webkit-unassigned barraclough darin ggaren max.hong.shen mjs oldest_to_newest 61014 0 eric 2007-11-12 13:32:32 -0800 JSObject needs getAsNumber to avoid costly string/number conversions This would be very useful for the bracket access operator on String when used in a numeric context, no create a substring to hold a single UChar. 61015 1 eric 2007-11-12 13:34:22 -0800 Funny, we were discussing this on Friday... re-editing what you wrote and having it come out in sentence fragments. I meant "a numeric context. There would then be no need to create a substring...". 61016 2 ggaren 2007-11-12 13:35:47 -0800 How does this fit in with "toNumber" and "getNumber"? What does getAsNumber return if the value is not a number? 61026 3 eric 2007-11-12 14:49:05 -0800 Hum... what I should have said was "getToNumber", since the idea behind all of the "evaluateToFoo" calls is that they're equivalent to to calling evaluate(exec)->toFoo(exec). I would want the same to hold true for any get variants. so this should be the awkward name, "getToNumber". I feel like I'm herding values or something... 713905 4 barraclough 2012-09-06 17:33:05 -0700 We do now have separate paths for string/numeric property access; I don't think this bug is still tracking a viable change.