Christopher Serr
Christopher Serr
Oh looks like #48 covers this.
target_pointer_width tells you nothing about whether f64 is natively supported or not.
This should be gated by a feature. It also probably will cause problems where libraries will attempt to spawn threads, so this is a breaking change in a way.
Yes there‘s wasm outside the browser, there‘s wasm in the browser, there‘s wasi and wasi in the browser. So those need to be handled differently (so 3 cases in total,...
> > However this will break many things regardless of that, as many libraries will start spawning threads if num_cpus > 1. > > I don't understand why this is...
I think I know exactly what's happening here: The game name on speedrun.com seems to end in a space, and LiveSplit, with the way XML works, strips all surrounding whitespace.
I'd say that we probably do want to fix this in LiveSplit somehow, since it's definitely a bug. However the space should almost definitely not be part of the game...
I definitely would want to run piccolo on wasmtime. I have a wasm based plugin system, so running Lua scripts via piccolo would be great.
```rust async move { x, y, z } { x } ``` would probably be ambiguous, otherwise I really like that syntax. Though arguably the `move` should be in front...
It seemed to be somewhere in the middle, sounded reasonable to me (also being a multiple of 60s), and with Rust being on the same level as C, that seemed...