Seems to match the pareto frontier on Artificial Analysis as well. Terra is nowhere on it.
> THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! This seems to be a common Chromium problem across tons of software. GitHub has the same issue with its spinners, VSCode as well.
This doesn't implement a JS engine, it's just a wrapper around boa.
Wasm can do 64-bit integers, SIMD and statically typed GC classes.
It depends. If you are compiling a high level GC language to WasmGC then there's really close to no reason why it would be larger than JS.
Keep an eye out for the algebraic operations on floats currently in nightly then: https://doc.rust-lang.org/nightly/std/primitive.f32.html#alg...
You can buffer overflow in fil-c and it won't detect it unless the entire buffer was its own stack or heap allocation with nothing following it (and also it needs to be a multiple of 16 bytes, cause that's padding that…
Ferrocene has donated their specification to the project, so there absolutely is a specification now. What you can argue is that the memory model isn‘t fully defined, but it‘s almost certainly going to land somewhere…
A ton of that is actually still doing codegen (for the proc macros for example).
WebAssembly also ended up calling its set of similar instructions relaxed.
I have an issue where I have two canvases that are overlapping and only WebKitGTK (not even just WebKit) just randomly stops showing one of the canvases.
First it was "Why Do Animals Keep Evolving into Crabs?", now it's "Why Do Programming Languages Keep Evolving into Crabs?"
I'd love to see VSCode integrate all the LSP information into Copilot. That seems to be the natural evolution of this idea.
It's 1.5x3 if you have a 21:9 screen. It's so bad.
There's no interpreter, I just map each instruction to equivalent Rust code. Linear memory is accessed through a trait. The compiler is here: https://github.com/CryZe/wasm-to-rust I have an example of a GameBoy emulator…
I once implemented a WASM to Rust compiler that due to WASM's safety compiles to fully safe Rust. So I was able to compile C -> WASM -> Rust and ended up with fully safe code. Though of course, just like in WASM, the C…
They are in the process of marking them safe, which is enabled through the target_feature 1.1 RFC. In fact, it has already been merged two weeks ago: https://github.com/rust-lang/stdarch/pull/1714 The change is already…
That was the time we learned about the changes to the block feature.
I still don't know why that isn't just provided for you.
> ability to use 64 bit types more easily Those are available on wasm32 just the same.
Only about 1/3 of those are language features. Out of those a ton are #[cfg] related (i.e. being able to more accurately doing conditional compilation), const (lifting limitations with compile time evaluation),…
> huge pain in the ass Maybe if you structure your code weirdly? I haven't encountered a major borrow checker issue that I couldn't easily resolve in many years.
Though arguably, the fact that in order to mutate data from multiple threads, the compiler,forces you to use some synchronization primitive, results in you having to think about how you are going to synchronize access,…
You definitely also get a lot more thread safety out of Rust than most languages.
Not mentioned in the blog post is the new addition of `size_of`, `size_of_val`, `align_of`, and `align_of_val` to the prelude, which means they don't need to be imported anymore:…
Seems to match the pareto frontier on Artificial Analysis as well. Terra is nowhere on it.
> THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! This seems to be a common Chromium problem across tons of software. GitHub has the same issue with its spinners, VSCode as well.
This doesn't implement a JS engine, it's just a wrapper around boa.
Wasm can do 64-bit integers, SIMD and statically typed GC classes.
It depends. If you are compiling a high level GC language to WasmGC then there's really close to no reason why it would be larger than JS.
Keep an eye out for the algebraic operations on floats currently in nightly then: https://doc.rust-lang.org/nightly/std/primitive.f32.html#alg...
You can buffer overflow in fil-c and it won't detect it unless the entire buffer was its own stack or heap allocation with nothing following it (and also it needs to be a multiple of 16 bytes, cause that's padding that…
Ferrocene has donated their specification to the project, so there absolutely is a specification now. What you can argue is that the memory model isn‘t fully defined, but it‘s almost certainly going to land somewhere…
A ton of that is actually still doing codegen (for the proc macros for example).
WebAssembly also ended up calling its set of similar instructions relaxed.
I have an issue where I have two canvases that are overlapping and only WebKitGTK (not even just WebKit) just randomly stops showing one of the canvases.
First it was "Why Do Animals Keep Evolving into Crabs?", now it's "Why Do Programming Languages Keep Evolving into Crabs?"
I'd love to see VSCode integrate all the LSP information into Copilot. That seems to be the natural evolution of this idea.
It's 1.5x3 if you have a 21:9 screen. It's so bad.
There's no interpreter, I just map each instruction to equivalent Rust code. Linear memory is accessed through a trait. The compiler is here: https://github.com/CryZe/wasm-to-rust I have an example of a GameBoy emulator…
I once implemented a WASM to Rust compiler that due to WASM's safety compiles to fully safe Rust. So I was able to compile C -> WASM -> Rust and ended up with fully safe code. Though of course, just like in WASM, the C…
They are in the process of marking them safe, which is enabled through the target_feature 1.1 RFC. In fact, it has already been merged two weeks ago: https://github.com/rust-lang/stdarch/pull/1714 The change is already…
That was the time we learned about the changes to the block feature.
I still don't know why that isn't just provided for you.
> ability to use 64 bit types more easily Those are available on wasm32 just the same.
Only about 1/3 of those are language features. Out of those a ton are #[cfg] related (i.e. being able to more accurately doing conditional compilation), const (lifting limitations with compile time evaluation),…
> huge pain in the ass Maybe if you structure your code weirdly? I haven't encountered a major borrow checker issue that I couldn't easily resolve in many years.
Though arguably, the fact that in order to mutate data from multiple threads, the compiler,forces you to use some synchronization primitive, results in you having to think about how you are going to synchronize access,…
You definitely also get a lot more thread safety out of Rust than most languages.
Not mentioned in the blog post is the new addition of `size_of`, `size_of_val`, `align_of`, and `align_of_val` to the prelude, which means they don't need to be imported anymore:…