Liam Murphy 46ea32f20e Revert #3248's changes to the wasm-in-web-worker example (#3278) ...

The start function still gets called on every thread in that example because it doesn't actually use wasm multithreading; each thread's instance has it's own separate memory pool and is completely unaware of the other thread. So, attempting to switch it to use a regular start function caused the worker thread to spawn another one, which does likewise, quickly spiralling out of control.

It also ended up panicking because, thinking it was the main thread, the code was trying to access `window` inside of a worker.

2023-02-02 09:29:11 -06:00

..

src

Revert #3248's changes to the wasm-in-web-worker example (#3278)

2023-02-02 09:29:11 -06:00

.gitignore

guide: Add the wasm-bindgen guide

2018-06-19 12:05:27 -07:00

book.toml

Update mdbook install

2019-06-19 13:49:57 -07:00