A Work-stealing Runtime for Rust - Aaron Toddair.mozilla.org1 points·by samnardoni·13 tahun yang lalu·0 comments
samnardoni·8 tahun yang lalu·discussWell, yes, that's true. But my point was that they aren't going to change the legacy nav data structure.
samnardoni·8 tahun yang lalu·discussHaving a pointer to a stack variable is fine, as long as the stack variable lives longer than the closure.
samnardoni·9 tahun yang lalu·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·9 tahun yang lalu·discussThe point is that wasm doesn't change this; wasm won't make it 'worse'.
samnardoni·10 tahun yang lalu·discussYou can write it both ways. t.method() is the same as T::method(t).
samnardoni·12 tahun yang lalu·discussRust uses LLVM, which does all the optimisation. Go generates the machine code itself and its optimisation is pretty weak compared to LLVM.
samnardoni·12 tahun yang lalu·discussWhy not profile and see where the time is actually going? Slow JSON parsing? Slow I/O?
samnardoni·12 tahun yang lalu·discussI think he/she meant the GC pauses were never longer than 100ms.