51–60 of 67 posts
Earlier quoted context omitted.
Isn't this what "editions" are supposed to handle, in part?
Editions are only necessary for otherwise-backwards-incompatible changes, to avoid breaking existing code. Even relatively major language features like the ? operator were shipped without an edition bump. But for example I think the await keyword itself was added as part of an edition, because it was incompatible with existing code that had a method named await. The messaging around the 2018 edition was a little diff…
Informally though, I think there are certainly a subset of people that use "Rust 2021" to mean all of the features included up to that point, even if it's not the precise definition.
Earlier quoted context omitted.
Code that predates the 2018 edition can have some cruft, especially with respect to the module system.
These are relatively minor things, and most of them can be cleaned up with `cargo fix` and `cargo clippy --fix`.
what word are people going to use after modern. it's kind of like using the word new. we don't use modern rust around here anymore, just modern new new modern rust.
A lot of people are getting really hung up on this. "Modern Rust" is just current Rust. Once Rust moves on, that will be modern Rust and what we once called modern will no longer be modern. Like all things. You might as well get upset that somebody said something will happen "tomorrow" because in 24 hours it won't be "tomorrow" anymore.
In particular, the intricate dependencies needed to do basic stuff, and choosing among many approaches.
This looks like a great resource, starred and upvoted. I'm planning to learn Rust next, going to start in a week after a job interview I had already lined up at Google. I worked with many languages professionally (JavaScript, TypeScript, Java, Python, Go, and now Dart) and many others at the university (C, C++, C#)... ...and Rust is very appealing to me. It's a modern language where the dev tools are straightforward,…
> I can't imagine that Rust will not be one of the most important languages of the next decade. As someone new to this industry, I'd love to hear a counter argument to this if anyone has one.
I can’t say I’ve ever known Rust very well, but I knew the basics and decided to wait and see before investing more time until there’s a clear sign that the language is becoming popular outside blockchain.
I don’t regret learning Rust, but haven’t seen any benefits either given my many years of C++ experience.
This looks like a great resource, starred and upvoted. I'm planning to learn Rust next, going to start in a week after a job interview I had already lined up at Google. I worked with many languages professionally (JavaScript, TypeScript, Java, Python, Go, and now Dart) and many others at the university (C, C++, C#)... ...and Rust is very appealing to me. It's a modern language where the dev tools are straightforward,…
> I can't imagine that Rust will not be one of the most important languages of the next decade. As someone new to this industry, I'd love to hear a counter argument to this if anyone has one.
Of course one can also use Rust for applications which previously used Java, and still benefit from a stricter type system and a potential efficiency improvement. But the selling proposition becomes a bit tougher. Con's for adopting Rust are the higher complexity, and a potentially reduced developer ecosystem for particular domains which have a ton of Java/C#/Go/Javascript libraries.
My first piece of advice is to just start writing code. If you are not specifically interested in super high performance systems level code, my second piece of advice would be to write code that avoids lifetime annotations until you get the basics of the borrow checker down. For me, this meant writing a gRPC API with Rust using `tonic` with a `diesel` based persistence backend and observability with `tracing` and `op…
My first piece of advice is to just start writing code. If you are not specifically interested in super high performance systems level code, my second piece of advice would be to write code that avoids lifetime annotations until you get the basics of the borrow checker down. For me, this meant writing a gRPC API with Rust using `tonic` with a `diesel` based persistence backend and observability with `tracing` and `op…
Slightly off topic question/comment: You are running an async server, together with a blocking database client? That sounds more like a very tricky place ot get started. Are you dispatching all your database queries into an extra threadpool?
This started to disgust me so I jumped to sqlx.
This looks like a great resource, starred and upvoted. I'm planning to learn Rust next, going to start in a week after a job interview I had already lined up at Google. I worked with many languages professionally (JavaScript, TypeScript, Java, Python, Go, and now Dart) and many others at the university (C, C++, C#)... ...and Rust is very appealing to me. It's a modern language where the dev tools are straightforward,…
We at Intervall are looking for excellent (Rust) developers: https://intervall.io/en/jobs.html#rust-developer
welp.