The (Unofficial) Blog-style Changelog for the V8 JavaScript Engine
No new features in this version.
No new features in this version.
This feature addresses a common pattern in software development regarding the lifetime and management of various resources (memory, I/O, etc.). This pattern generally includes the allocation of a resource and the ability to explicitly release critical resources.
{
"category": "JavaScript",
"flag_name": null,
"id": 5087324181102592,
"milestone": 133,
"name": "Explicit resource management (async)",
"summary": "This feature addresses a common pattern in software development regarding the lifetime and management of various resources (memory, I/O, etc.). This pattern generally includes the allocation of a resource and the ability to explicitly release critical resources."
}Adds the Atomics.pause method to hint the CPU that the current code is executing a spinlock.
{
"category": "JavaScript",
"flag_name": "--js-atomics-pause",
"id": 5106098833719296,
"milestone": 133,
"name": "Atomics.pause",
"summary": "Adds the Atomics.pause method to hint the CPU that the current code is executing a spinlock."
}This feature adds an "overallProgress" property to the JavaScript class Animation[1]. The goal of this property is provide authors a convenient and consistent representation of how far along an animation has advanced across its iterations and regardless of the nature of its timeline[2]. [1] https://developer.mozilla.org/en-US/docs/Web/API/Animation [2] https://developer.mozilla.org/en-US/docs/Web/API/AnimationTimeline
{
"category": "JavaScript",
"flag_name": "AnimationProgressAPI",
"id": 5083257285378048,
"milestone": 133,
"name": "Animation.overallProgress",
"summary": "This feature adds an \"overallProgress\" property to the JavaScript class Animation[1].\n\nThe goal of this property is provide authors a convenient and consistent representation of how far along an animation has advanced across its iterations and regardless of the nature of its timeline[2].\n\n[1] https://developer.mozilla.org/en-US/docs/Web/API/Animation\n[2] https://developer.mozilla.org/en-US/docs/Web/API/AnimationTimeline"
}Intl Locale Info API is a Stage 3 ECMAScript TC39 proposal to enhance the Intl.Locale object by exposing Locale information, such as week data (first day in a week, weekend start day, weekend end day, minimun day in the first week), and text direction hour cycle used in the locale. https://github.com/tc39/proposal-intl-locale-info We ship our implementation in m99 (https://chromestatus.com/feature/5566859262820352 ) . But later on the propose made some change in Stage 3 and move several getters to functions. We need to remove the deprecated getters and relaunch the renamed functions
{
"category": "JavaScript",
"flag_name": "harmony_remove_intl_locale_info_getters",
"id": 5148228059398144,
"milestone": 133,
"name": "Deprecate getters of Intl Locale Info",
"summary": "Intl Locale Info API is a Stage 3 ECMAScript TC39 proposal to enhance the Intl.Locale object by exposing Locale information, such as week data (first day in a week, weekend start day, weekend end day, minimun day in the first week), and text direction hour cycle used in the locale.\r\nhttps://github.com/tc39/proposal-intl-locale-info\r\n\r\nWe ship our implementation in m99 (https://chromestatus.com/feature/5566859262820352 ) . But later on the propose made some change in Stage 3 and move several getters to functions. We need to remove the deprecated getters and relaunch the renamed functions\r\n"
}This feature addresses a common pattern in software development regarding the lifetime and management of various resources (memory, I/O, etc.). This pattern generally includes the allocation of a resource and the ability to explicitly release critical resources.
{
"category": "JavaScript",
"flag_name": null,
"id": 5071680358842368,
"milestone": 133,
"name": "Explicit resource management (sync)",
"summary": "This feature addresses a common pattern in software development regarding the lifetime and management of various resources (memory, I/O, etc.). This pattern generally includes the allocation of a resource and the ability to explicitly release critical resources."
}The memory64 proposal adds support for linear WebAssembly memories with size larger than 2^32 bits. It provides no new instructions, but instead extends the existing instructions to allow 64-bit indexes for memories and tables.
{
"category": "WebAssembly",
"flag_name": "enable-experimental-webassembly-features",
"id": 5070065734516736,
"milestone": 133,
"name": "WebAssembly Memory64",
"summary": "The memory64 proposal adds support for linear WebAssembly memories with size larger than 2^32 bits. It provides no new instructions, but instead extends the existing instructions to allow 64-bit indexes for memories and tables."
}