A Work-stealing Runtime for Rust - Aaron Toddair.mozilla.org1 points·by samnardoni·hace 13 años·0 comments
samnardoni·hace 8 años·discussWell, yes, that's true. But my point was that they aren't going to change the legacy nav data structure.
samnardoni·hace 8 años·discussHaving a pointer to a stack variable is fine, as long as the stack variable lives longer than the closure.
samnardoni·hace 9 años·discussYou can do all that with JS too. Wasm adds nothing extra. It's perfectly sensible to imagine wasm applications targeting the DOM (which it can do via JS, and will do natively in later releases) just like JS applications do now.
samnardoni·hace 9 años·discussThe point is that wasm doesn't change this; wasm won't make it 'worse'.
samnardoni·hace 12 años·discussRust uses LLVM, which does all the optimisation. Go generates the machine code itself and its optimisation is pretty weak compared to LLVM.
samnardoni·hace 12 años·discussWhy not profile and see where the time is actually going? Slow JSON parsing? Slow I/O?