@mraleph Go v8! :) Brought the comment to the list too. @slightlylate
-
-
Replying to @olov1 reply 0 retweets 0 likes
-
Replying to @slightlylate
@slightlylate@olov sitatuation with accessors in V8 still can be improved, I think it is still bad perf if accessors are on obj itself2 replies 0 retweets 0 likes -
Replying to @mraleph
@mraleph I gave simple .H some more thought. Why wouldn't a compiler be able to elide most writes to it with my step 5?@slightlylate1 reply 0 retweets 0 likes -
Replying to @olov
@olov it would not be able for the last operation in a sequence because value always leaks outside@slightlylate1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@olov you don't want to leak intermediate value anywhere. it becomes complex to avoid the memory store in this case1 reply 0 retweets 0 likes -
Replying to @mraleph2 replies 0 retweets 0 likes
-
Replying to @slightlylate
@slightlylate@olov I would say returning {lo, hi} object would be good if we did not need to worry about polyfill perf vs. state of art.2 replies 0 retweets 0 likes -
Replying to @mraleph
@mraleph agreed, but I don't think we can afford not to worry about polyfilled perf if we want to see this API adopted..@slightlylate1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.