I hadn't heard about that, but it sounds awesome
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
miri is better at determinism and isolation though, its allocations are symbolic, while wasm is concrete in a sense, miri is more objcap than wasm only good reason not to use miri IMO, is interpreting cost could be alleviated by monomorphizing on the fly, but unsure
I meant: those are advantages over compiled MIR. We don't want to download proc macros as MIR and finish compiling them because no determinism and isolation and it's slow. We don't want to download proc macros as MIR and interpret them because it's slow too.
-
-
aaah. there is a misunderstanding here, too you couldn't do this even if you wanted to because everything after parsing (macros, types, MIR, etc) depends on the target chosen unless you have .rmeta for a fixed target like wasm32, I guess
-
We could if we wanted to, because in practice the overwhelming majority of http://crates.io requests are probably for a pretty small set of targets. You could precompile MIR for those. Perfect shouldn't be the enemy of improving compile time for 99% of users!
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.