wasmex changelog

Changelog History

• v0.3.1 Changes

  April 04, 2021

  ➕ Added

  • ➕ added support for aarch64-darwin (apple silicon). Thanks @epellis

  🔄 Changed

  • ✂ removed use of unsafe from wasm<->elixir value conversion. Thanks @Virviil

• v0.3.0

  January 09, 2021

• v0.2.0 Changes

  April 14, 2020

  🚀 This release brings is closer to a production-ready experience. Calls of WebAssembly functions are now handled asynchronously: Invoking a WASM function via Instance.call_exported_function calls our Rust NIF as before, but does not directly execute the function. Instead, a new OS thread is spawned for the actual execution. This allows us to spend only few time in the NIF code (as required by the Erlang VM). Once the WASM function in that thread returns, we send a message to the calling erlang process. 🔀 To ease handling, we converted our main module Wasmex into a GenServer so that a WASM function call can be used in a synchronous manner as before.

  ➕ Added

  • The Wasmex module is now a GenServer. WASM function calls are now asynchronous.

  🔄 Changed

  • ✂ Removed unused Rust dependencies
  • 👍 Provide better error messages for Wasmex.Instance.from_bytes when the WASM instance could not be instantiated.
  • 👍 WASM function calls now return a list of return values instead of just one value (this is to prepare for WASM tu officially support multiple return values)
  • ⚡️ Updated elixir and rust dependencies including wasmer to version 0.16.2

  ✂ Removed

  • Instance.call_exported_function/2 use Instance.call_exported_function/3 instead.

  🛠 Fixed

  • ✨ Enhanced documentation

• v0.1.0 Changes

  January 15, 2020

  🔄 Changed

  • 🚀 First release