Re: [v8-users] Microoptimizing message handling

2019-04-23 Thread Ben Noordhuis
On Fri, Apr 19, 2019 at 9:16 AM J Decker wrote: > > A question came to mind about the resolution of the 'compilation' of code.. I > have message handlers that receive an object with a standard field 'op'. > Then for each 'op' that can be processed I have an if test and a small amount > of

Re: [v8-users] Microoptimizing message handling

2019-04-23 Thread Jakob Kummerow
Optimized compilation happens on a per-function basis. A large function with many branches (if/else or switch), some of which are only executed rarely, tends to cause repeated deoptimizations (some branches have been executed enough to make the function hot, it gets optimized, then one of the

[v8-users] Re: [v8-dev] Intent to Ship: Promise.allSettled

2019-04-23 Thread Adam Klein
LGTM! On Tue, Apr 23, 2019 at 4:19 PM Sathya Gunasekaran wrote: > Contact Emails: > gsat...@chromium.org > > Spec: > https://tc39.github.io/proposal-promise-allSettled/ > > Summary: > Promise.allSettled returns a promise that is fulfilled with an array > of promise state snapshots, but only

[v8-users] Intent to Ship: Promise.allSettled

2019-04-23 Thread Sathya Gunasekaran
Contact Emails: gsat...@chromium.org Spec: https://tc39.github.io/proposal-promise-allSettled/ Summary: Promise.allSettled returns a promise that is fulfilled with an array of promise state snapshots, but only after all the original promises have settled, i.e. become either fulfilled or