On 2015/07/14 16:18:54, adamk wrote:
Given that we have what looks like a small fix (after caitp's helpful
pointer
to
where my code was busted), do we not want to give a shot at merging a fix
to
this on the branch? If we were happy with shipping this before this bug
was
known, I don't know why we'd be less happy to try to ship it with this bug
fixed. Unless we just want to have a blanket policy of "if a flag can be
flipped
to fix a bug on branch, always do that."
WDYT?
I think it's too late. The features already got removed from the M45 blog
post.
The fix would need some bake time. I rather don't want to cause more back &
forth. There is no rush, we can ship it in 46 (it actually makes a nice
package
with destructuring).
https://codereview.chromium.org/1230773005/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
