The JavaScript engine communicates faster with the V8 9.0.0 webseable

Google’s JavaScript engine V8 gets a new release with 9.0. The ninth major edition marks the beginning of a new branch. The current V8 version will hold beta status until the next Chrome release is stable under version 90.

Match schedule for regular expressions

V89 Introduces the Competitive Code for Regular Expressions (RegExp). Developers have the opportunity to call a queue with the initial and final stages of the capture team associated with the competition with RegExp. The queue is via property .indices Match items will be available if the flag is in regular expression /d Hat.

What’s new is you can use the keyword super Can now be used to access the properties and functions of the parent object. Until now, access to a super property (e.g. super.x) Is activated via a runtime call. With the V8 9.0, the inline cache system (IC) is used in the optimized code, which generates the corresponding optimal code for accessing the super property without seeking runtime. This increases the speed of accessing the properties.

JavaScript and WebAsable

In the past, performance when calling JavaScript for WebSecial was fine because V8 uses different display formats for parameters of WebSebel and JavaScript functions. When JavaScript calls the exported webable function, the call runs through a so-called JS-to-Wasm wrapper, which ensures that the parameters are adjusted from JavaScript to webselling – and vice versa. With the update, the JS-to-Wasm wrapper now has an embedded (inline) option during call, which is intended to simplify the code and remove this extra frame. This is a test feature, what about the flag --turbo-inline-js-wasm-calls Can be disabled.

Due to a recent discovery Grammatical ambiguity Becomes a token queue for for (async of No longer parsed. Additional information about the latest version of the JavaScript engine Can be found in the post on the V8 blog.

(mdo)