11–20 of 215 posts
Incremental compilation turned on by default :-)
> Historically, the compiler has compiled your entire project, no matter how little you’ve changed the code.
This isn't quite correct. When you change the code in a given library, it has historically recompiled that entire library, and all libraries that depend on that library. But the compiler has never recompiled any libraries that were deeper in the dependency chain: if you have crates foo and bar, and bar imports foo, and you change the code in bar, foo was not recompiled.
Looking towards the future, I'm most excited about the prospect of using SIMD on stable Rust, which looks to be coming this year: https://github.com/rust-lang/rfcs/pull/2325
EDIT: Also worth mentioning is that Rayon (an official Rust library providing easy data parallelism) just reached 1.0 today, which is an important milestone in Rust's march towards ecosystem stability: https://github.com/rayon-rs/rayon
Incremental compilation turned on by default :-)
Hmm... when I read that, I got excited thinking it would be like Common Lisp's, where the idea is to incrementally compile in changes to a running program, to the effect of being able to see the effects without having to restart it. This just sounds like what Makefiles do, but at a sub-file/AST level.
Your analogy to Makefiles is right in a big-picture sense. In the small, it's different, but you've got the big idea correct.
Incremental compilation! And it's only going to incremental-er from here, as the compiler learns how to cache more and more sorts of interim artifacts to avoid redundant work. Though I think the wording in the OP is a bit off: > Historically, the compiler has compiled your entire project, no matter how little you’ve changed the code. This isn't quite correct. When you change the code in a given library, it has histor…
Can someone sell me on using rust over python? I am just gernerally curious as to the advantage beyond rust being compiled.
Can someone sell me on using rust over python? I am just gernerally curious as to the advantage beyond rust being compiled.
That said, development time in Python is much faster.
Honestly, it depends on what you're building.
Incremental compilation! And it's only going to incremental-er from here, as the compiler learns how to cache more and more sorts of interim artifacts to avoid redundant work. Though I think the wording in the OP is a bit off: > Historically, the compiler has compiled your entire project, no matter how little you’ve changed the code. This isn't quite correct. When you change the code in a given library, it has histor…
Have there been any thoughts around making the compiler something akin to a stateful server with an embedded datastore for the caching rather than using the filesystem?
Can someone sell me on using rust over python? I am just gernerally curious as to the advantage beyond rust being compiled.
You could write parts of a network server or parts of an OS kernel in python. You could write nearly the entirety of it in rust.
I would say that you need not use rust if python works well for you, but rust is probably better than C for implementing libraries that might be called from python.