FYI-
My first attempt sent from ft...@google.com got bounced back. Trying to
forward from ft...@chromium.org.
Sorry for the DUP
-- Forwarded message -
From: 'Frank Tang (譚永鋒)' via v8-dev
Date: Tue, Feb 19, 2019 at 9:59 PM
Subject: [v8-dev] Intent to ship: Intl.Locale
To: , , <
I'm fairly certain this no longer the case, and you stop avoiding try/catch.
https://github.com/tildeio/rsvp.js/pull/539
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
Hi,
I have read in some online posts that try/catch will stop v8 to optimize
the code. I that still the case even in latest version of v8?
What are solutions to get better performance for the code inside
try/catch block?
Thanks
--
--
v8-users mailing list
v8-users@googlegroups.com
Hi,
I saw that *IdleNotificationDeadline()* in term invokes
*Heap::PerformIdleTimeAction() (heap.cc), *
And in case of `action.type == DO_NOTHING` it will return false.
So ArangoDB kept on invoking IdleNotificationDeadline() without any effect.
Did we set up the preconditions wrong (so type
*TLDR: we are planning to remove support for nosnapshot builds (gn flag:
'v8_use_snapshot = false') and builds without embedded builtins (gn flag:
'v8_enable_embedded_builtins = false').*
*Snapshot?*
Currently, V8 supports building with- and without a snapshot