Alex Crichton e46537e6c2 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.		2018-10-10 15:47:07 -07:00
..
ast.rs	Parse Paths in extends attributes	2018-10-03 09:14:23 -07:00
codegen.rs	Ensure that JsValue isn't considered Send	2018-10-10 15:47:07 -07:00
defined.rs	Parse Paths in extends attributes	2018-10-03 09:14:23 -07:00
error.rs	cargo +nightly fmt --all	2018-09-26 08:26:00 -07:00
lib.rs	cargo +nightly fmt --all	2018-09-26 08:26:00 -07:00
util.rs	cargo +nightly fmt --all	2018-09-26 08:26:00 -07:00