We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
In the current changelog, for 3.1.74, there's content missing for one of the changes. (I added emphasis)
3.1.74 - 12/14/24 The file system was updated to independently track atime, mtime and ctime instead of using the same time for all three. (JS file system: distinguish between atime, mtime, and ctime #22998) Emscripten-generated code will now use async/await internally when loading the Wasm module. This will be lowered away by babel when targeting older browsers. (Use async/await instead of promises for wasm loading. NFC #23068) Due to the discontinued support for invalid specializations of std::basic_string ([libc++] Remove deprecated char_traits base template llvm/llvm-project#72694), the support for std::basic_string<unsigned char> was removed from embind. (Remove basic_string<unsigned char> from embind #23070) The minimum supported versions of browser engines that we support were updated to versions that support Promise, Fetch and Object.asign APIs, allowing the polyfills for these to be removed. Chrome 32 -> 45, Firefox 34 -> 40, Safari 9.0 -> 10.1. These browser engines version are all over 8 years old now. (Bump minimum supported chrome version from 32 to 33 #23077, Remove polyfills for Fetch and Object.assign #23118)
std::basic_string
std::basic_string<unsigned char>
The text was updated successfully, but these errors were encountered:
Thanks, looks like there is an unneeded bullet point there, from #23070
#23181 will fix it.
Sorry, something went wrong.
658feba
[NFC] Remove confusing bullet point in changelog (emscripten-core#23181)
efea9d0
Fixes emscripten-core#23178
Successfully merging a pull request may close this issue.
In the current changelog, for 3.1.74, there's content missing for one of the changes. (I added emphasis)
The text was updated successfully, but these errors were encountered: