Wasmbind

Latest version: v0.4

Safety actively analyzes 626513 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 10

0.2.25

Released 2018-10-10.

Fixed

* Using `wasm-bindgen` will no longer unconditionally pull in Rust's default
allocator for Wasm (dlmalloc) regardless if you configured a custom global
allocator (eg wee_alloc).
[947](https://github.com/rustwasm/wasm-bindgen/pull/947)

* Fixed web-sys build on some Windows machines.
[943](https://github.com/rustwasm/wasm-bindgen/issues/943)

* Fixed generated ES class bindings to Rust structs that were only referenced
through struct fields.
[948](https://github.com/rustwasm/wasm-bindgen/issues/948)

--------------------------------------------------------------------------------

0.2.24

Released 2018-10-05.

Added

* Constructors for types in `web-sys` should now have better documentation.

* A new `vendor_prefix` attribute in `[wasm_bindgen]` is supported to bind APIs
on the web which may have a vendor prefix (like `webkitAudioContext`). This is
then subsequently used to fix `AudioContext` usage in Safari.

* The `[wasm_bindgen(extends = Foo)]` attribute now supports full paths, so you
can also say `[wasm_bindgen(extends = foo::Bar)]` and such.

Changed

* The `Closure<T>` type is now optimized when the underlying closure is a ZST.
The type now no longer allocates memory in this situation.

* The documentation now has a list of caveats for browser support, including how
`TextEncoder` and `TextDecoder` are not implemented in Edge. If you're using
webpack there's a listed strategy available, and improvements to the polyfill
strategy are always welcome!

* The `BaseAudioContext` and `AudioScheduledSourceNode` types in `web-sys` have
been deprecated as they don't exist in Safari or Edge.

Fixed

* Fixed the `[wasm_bindgen_test]`'s error messages in a browser to correctly
escape HTML-looking output.

* WebIDL Attributes on `Window` are now correctly bound to not go through
`Window.prototype` which doesn't exist but instead use a `structural`
definition.

* Fixed a codegen error when the `BorrowMut` trait was in scope.

* Fixed TypeScript generation for constructors of classes, it was accidentally
producing a syntactially invalid file!

--------------------------------------------------------------------------------

0.2.23

Released 2018-09-26.

Added

* [This is the first release of the `web-sys`
crate!](https://rustwasm.github.io/2018/09/26/announcing-web-sys.html)

* Added support for unions of interfaces and non-interfaces in the WebIDL
frontend.

* Added a policy for inclusion of new ECMAScript features in `js-sys`: the
feature must be in stage 4 or greater for us to support it.

* Added some documentation about size profiling and optimization with
`wasm-bindgen` to the guide.

* Added the `Clamped<T>` type for generating JavaScript `Uint8ClampedArray`s.

* CI is now running on beta! Can't wait for the `rustc` release trains to roll
over, so we can run CI on stable too!

* Added the `js_sys::try_iter` function, which checks arbitrary JS values for
compliance with the JS iteration protocol, and if they are iterable, converts
them into an iterator over the JS values that they yield.

Changed

* We now only generate null checks on methods on the JS side when in debug
mode. For safety we will always null check on the Rust side, however.

* Improved error messages when defining setters that don't start with `set_` and
don't use `js_name = ...`.

* Improved generated code for classes in a way that avoids an unnecessary
allocation with static methods that return `Self` but are not the "main"
constructor.

* **BREAKING:** `js_sys::Reflect` APIs are all fallible now. This is because
reflecting on `Proxy`s whose trap handlers throw an exception can cause any of
the reflection APIs to throw. Accordingly, `js_sys` has been bumped from
`0.2.X` to `0.3.X`.

Fixed

* The method of ensuring that `__wbindgen_malloc` and `__wbindgen_free` are
always emitted in the `.wasm` binary, regardless of seeming reachability is
now zero-overhead.

--------------------------------------------------------------------------------

0.2.22

Released 2018-09-21

Added

* The `IntoIterator` trait is now implemented for JS `Iterator` types
* A number of variadic methods in `js-sys` have had explicit arities added.
* The guide has been improved quite a bit as well as enhanced with more examples
* The `js-sys` crate is now complete! Thanks so much to everyone involved to
help fill out all the APIs.
* Exported Rust functions with `[wasm_bindgen]` can now return a `Result` where
the `Err` payload is raised as an exception in JS.

Fixed

* An issue with running `wasm-bindgen` on crates that have been compiled with
LTO has been resolved.

--------------------------------------------------------------------------------

0.2.21

Released 2018-09-07

Added

* Added many more bindings for `WebAssembly` in the `js-sys` crate.

Fixed

* The "names" section of the wasm binary is now correctly preserved by
wasm-bindgen.

--------------------------------------------------------------------------------

0.2.20

Released 2018-09-06

Added

* All of `wasm-bindgen` is configured to compile on stable Rust as of the
upcoming 1.30.0 release, scheduled for October 25, 2018.
* The underlying `JsValue` of a `Closure<T>` type can now be extracted at any
time.
* Initial and experimental support was added for modules that have shared memory
(use atomic instructions).

Removed

* The `--wasm2asm` flag of `wasm2es6js` was removed because the `wasm2asm` tool
has been removed from upstream Binaryen. This is replaced with the new
`wasm2js` tool from Binaryen.

Fixed

* The "schema" version for wasm-bindgen now changes on all publishes, meaning we
can't forget to update it. This means that the crate version and CLI version
must exactly match.
* The `wasm-bindgen` crate now has a `links` key which forbids multiple versions
of `wasm-bindgen` from being linked into a dependency graph, fixing obscure
linking errors with a more first-class error message.
* Binary releases for Windows has been fixed.

--------------------------------------------------------------------------------

Page 8 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.