Earlier quoted context omitted.
Many examples out there are broken. As a sidenote, I've been benchmarking Zig, Rust and C++ with a fibonacci benchmark and the results basically show that C++ is the fastest, but within a 3% margin of error against Rust and Zig, which are mostly similar (Rust so ever slightly faster).
Can you please share the code? On my tests late last year it was basically Zig, C++, Rust. Sorry I don’t have the code anymore.
Zig 0.13.0 Release Notes
21–25 of 25 posts
Re: Zig 0.13.0 Release Notes
#22Earlier quoted context omitted.
Many examples out there are broken. As a sidenote, I've been benchmarking Zig, Rust and C++ with a fibonacci benchmark and the results basically show that C++ is the fastest, but within a 3% margin of error against Rust and Zig, which are mostly similar (Rust so ever slightly faster).
What's compiling C++? Having faster compilers available is nice, but comparing same llvm version would be interesting
Re: Zig 0.13.0 Release Notes
#23Earlier quoted context omitted.
Many examples out there are broken. As a sidenote, I've been benchmarking Zig, Rust and C++ with a fibonacci benchmark and the results basically show that C++ is the fastest, but within a 3% margin of error against Rust and Zig, which are mostly similar (Rust so ever slightly faster).
Have you published these benchmarks?
Re: Zig 0.13.0 Release Notes
#24Earlier quoted context omitted.
Here too? Never mind function colouring, async/await itself is a feature that infects entire languages. Such a terrible abstraction of concurrency for our 1970-style languages. Zig doesn't have strings because they're too high level, but async/await is fine.
From what we know their async/await should be noticeably distinct from the usual, otherwise the previous revert was for nothing.
Re: Zig 0.13.0 Release Notes
#25Earlier quoted context omitted.
From what we know their async/await should be noticeably distinct from the usual, otherwise the previous revert was for nothing.
I still can't find a decent explanation as to why zig, a C replacement needs to have Async built in by default. I actually think this should belong to a higher level abstraction.
As for the correct level of abstraction of async/await I believe that it's actually a very low-level primitive that should only be offered in low-level languages as it's very footgunny to use in high-level languages and generally worse than actors/csp.