Now that you can compile and run tests, how performant are they compared to rustc+llvm? I know that thinLTO is not yet enable, and I guess a few other important optimisation, but I'm interested to know what we can already get.
robinm
joined 2 years ago
This is incredible. Congrats!
I totally get the = async { body } (and I think I would prefer it for everything since it makes one liner like fn add(a: i32, b: i32) -> i32 = a+b much nicer and compact). I can also get the "ignore associated type” part. But I fail to see why removing the impl in -> impl Future is useful.
Isn't China also building a lot fission power plants atm?
Those side channels attacks are fascinating
It's something that I never understood for other certified toolchain. What is a value of a certified toolchain containing known bugs, including critical and/or security bugs that are fixed upstream?
What ferrous systems does is trully great!
And throwing out an online birthday party is a nice idea. See you there.
With both Linux and Windows actively using Rust, it really seems that this language has proved its qualities.
Just toebe sure, what's the name of this new terminal emulator? termkit?
That's very nice! I really hope that at one point, thumb-key will be able support circle and back-and-forth gesture. That's the only thing blocking me from migrating from messagEase.
That's true. But at least you will have evidence that Martin doesn't conform to the team rules.
Yes exacly. And I assume that the test suite of all of those project are long enough to average the usual jitter of wall time mesurement.
What I'm hoping to see is if rust+llvm vs rustc+gcc binary speed are within a few percents or if there is a real difference between the two (I'm expected that we eventually reach the former once thinLTO and other optimisations are implemented).
And while doing so it could also be possible to measure the difference in max RSS.