Rust 1.60.0(blog.rust-lang.org)
blog.rust-lang.org
Rust 1.60.0
https://blog.rust-lang.org/2022/04/07/Rust-1.60.0.html
10 comments
> Incremental compilation is re-enabled for the 1.60 release. The Rust team continues to work on fixing bugs in incremental, but no problems causing widespread breakage are known at this time, so we have chosen to reenable incremental compilation.
Wow that is concerning, if it is buggy, you don't enable it by default
Wow that is concerning, if it is buggy, you don't enable it by default
Everything is buggy. Welcome to software.
Thankfully i don't agree with that, all yours, the buggy software
I like how easy Go is to learn and how simple it is (along with the library availability) but can't help but feel that Rust feels more "put together" especially in the type system and Generics areas. I feel like I am using a real language instead of a toy.
Didn't one of Go's founders specifically say they didn't want to take advantage of existing type theory, in the name of "simplicity"? Meanwhile Rust is building off the ML/OCaml tradition. No wonder the language building on a 40 year body of work feels more consistent.
It's not from a founder, but I like this paragraph from the preface of The Go Programming Language:
Go has enough of a type system to avoid most of the careless mistakes that plague programmers in dynamic languages, but it has a simpler type system than comparable typed languages. This approach can sometimes lead to isolated pockets of "untyped" programming within a broader framework of types, and Go programmers do not go to the lengths that C++ or Haskell programmers do to express safety properties as type-based proofs. But in practice Go gives programmers much of the safety and run-time performance benefits of a relatively strong type system without the burden of a complex one.
I happen to like this idea of gaining safety through the type system. Sometime's when Go's frustrating me I have to remember - it's that I'm be expecting and achieve something it just isn't intended for.
Go has enough of a type system to avoid most of the careless mistakes that plague programmers in dynamic languages, but it has a simpler type system than comparable typed languages. This approach can sometimes lead to isolated pockets of "untyped" programming within a broader framework of types, and Go programmers do not go to the lengths that C++ or Haskell programmers do to express safety properties as type-based proofs. But in practice Go gives programmers much of the safety and run-time performance benefits of a relatively strong type system without the burden of a complex one.
I happen to like this idea of gaining safety through the type system. Sometime's when Go's frustrating me I have to remember - it's that I'm be expecting and achieve something it just isn't intended for.
I do think there's a degree of "as simple as possible, but no simpler". But also to be fair, Rust's target use cases lean harder towards max performance and max correctness, at the expense of learning curve and (sometimes) dev time.
This is great! It makes things more manageable for third-party implementations like mrustc and gcc-rust, for teaching resources that can spend time improving their docs on what's already there instead of documenting new stuff, and for the long-term health of the language itself. Here's for many more releases like this one!