Skip to content

Move proxying change to correct location in ChangeLog.md #19132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tlively merged 1 commit into from
Apr 4, 2023
Merged

Move proxying change to correct location in ChangeLog.md #19132

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions ChangeLog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,9 @@ See docs/process.md for more on how version tagging works.
- The WasmFS OPFS backend is now faster in browsers that implement
[`Atomics.waitAsync`](https://caniuse.com/mdn-javascript_builtins_atomics_waitasync).
(#18861)
- The `emscripten_proxy_async_with_callback` API was replaced with a simpler
`emscripten_proxy_callback` API that takes a second callback to be called if
the worker thread dies before completing the proxied work.

3.1.32 - 02/17/23
-----------------
Expand All @@ -101,9 +104,6 @@ See docs/process.md for more on how version tagging works.
- Synchronous proxying functions in emscripten/proxying.h now return errors
instead of hanging forever when the worker thread dies before the proxied work
is finished.
- The `emscripten_proxy_async_with_callback` API was replaced with a simpler
`emscripten_proxy_callback` API that takes a second callback to be called if
the worker thread dies before completing the proxied work.

3.1.31 - 01/26/23
-----------------
Expand Down