Commits on Oct 10, 2018

1. Ensure that JsValue isn't considered Send …

   The `JsValue` type wraps a slab/heap of js objects which is managed by
   the wasm-bindgen shim, and everything here is not actually able to cross
   any thread boundaries. When wasm actually has threads, for example, each
   thread will have to have its own slab of objects generated by
   wasm-bindgen, and indices in one slab aren't valid in any other slabs.
   
   This is technically a breaking change because `JsValue` was previously
   `Send` and `Sync`, but I'm hoping that in practice this isn't actually a
   breaking change because nothing in wasm can be using threads which in
   theory shouldn't activate the `Send` and/or `Sync` bounds.

   

   alexcrichton committed Oct 10, 2018
   Configuration menu

   • View commit details
   • Copy full SHA for e46537e
   • Browse repository at this point

   Copy the full SHA

   e46537e View commit details

   Browse the repository at this point in the history