241–250 of 303 posts
One great thing about the Rust books and tutorial -- you can easily enjoy them offline, right out-of-the-box. I learned the basics of Rust on a long plane ride with no WiFi. What a great way to pass the time!
“How” is the stupidest word to auto-censor. Removing it completely changes the meaning of titles. It makes articles seem vapid or banal when they wouldn’t otherwise, and vice versa.
The danger with these arguments is that you only notice the cases that don't work. That's a 100% failure rate! Can't get more stupid than that!
pg suggested this edit to me years ago and I spent a long time back testing it on old titles. At the time, it was a clear win. I suppose it's possible that title conventions have changed since then and taking another look might be a good idea.
Serious question: can I just use smart pointer like feature of Rc/Arc combing with Mutex or RWLock instead of fighting borrow checker? I know this practice is shunned upon by Rust purists but I like to see how practical it is in real life and project. Especially around using Rust as a safer but more performant language instead of pushing for ultimate zero-cost abstraction and top notch performance.
The idea is that once you are familiar with other aspects of the language (syntax, sum types, traits, modules), you can go back and try to master the borrow checker.
One great thing about the Rust books and tutorial -- you can easily enjoy them offline, right out-of-the-box. I learned the basics of Rust on a long plane ride with no WiFi. What a great way to pass the time!
I don't see anything explicitly calling out what to download in nonethewiser's link. How did you end up grabbing these things for offline learning?
“The HTML format is available online at https://doc.rust-lang.org/stable/book/ and offline with installations of Rust made with rustup; run rustup docs --book to open“
More importantly, it has a “next page” arrow at the bottom right, and a TOC pop-up at the top left of the page.
One great thing about the Rust books and tutorial -- you can easily enjoy them offline, right out-of-the-box. I learned the basics of Rust on a long plane ride with no WiFi. What a great way to pass the time!
I don't see anything explicitly calling out what to download in nonethewiser's link. How did you end up grabbing these things for offline learning?
rustup docs --book
One great thing about the Rust books and tutorial -- you can easily enjoy them offline, right out-of-the-box. I learned the basics of Rust on a long plane ride with no WiFi. What a great way to pass the time!
I don't see anything explicitly calling out what to download in nonethewiser's link. How did you end up grabbing these things for offline learning?
Earlier quoted context omitted.
The compiler would enforce Number-ness every time I try and run a function that takes a number, right? Wouldn’t I still have to check for NoScore? > a sum type with units of Score(Int) and NoScore won't allow assignments of any other "null" instances. I get this part - I wouldn’t be able to assign ‘NewBornBaby’ (my name null) to ‘NoScore’ (my score null)
>Wouldn’t I still have to check for NoScore? That's right, and the compiler will reject programs where you don't do this. It's a set of safety rails for your code. You pay a dev-/compile-time cost in exchange for your programs not exploding at runtime.
> In your example, you still have to manually check if there's a value every time, but this is not compiler-enforced.
Earlier quoted context omitted.
The compiler would enforce Number-ness every time I try and run a function that takes a number, right? Wouldn’t I still have to check for NoScore? > a sum type with units of Score(Int) and NoScore won't allow assignments of any other "null" instances. I get this part - I wouldn’t be able to assign ‘NewBornBaby’ (my name null) to ‘NoScore’ (my score null)
> The compiler would enforce Number-ness every time I try and run a function that takes a number, right? > Wouldn’t I still have to check for NoScore? No, because you differentiate between the sum type (e.g. Maybe in Haskell) and the number type at compile time. It's a small distinction - there will still be one or two places where you ask "is this a Maybe-score, or a Just-Score, or a No-Score", but the upside is tha…
If I pass a null into something that calculates an average, taking numbers, the TS compiler will complain now. The writer of mean() (assuming mean() is typed) doesn’t have to know anything about my code.
One great thing about the Rust books and tutorial -- you can easily enjoy them offline, right out-of-the-box. I learned the basics of Rust on a long plane ride with no WiFi. What a great way to pass the time!
This sounded interesting but I was confused by what you meant by "the book." Looks like that's how it's commonly referred to https://www.rust-lang.org/learn
Earlier quoted context omitted.
Rust is the more elegant and powerful language. Creating a new language and repeating the "billion dollar mistake" by including null (sailing under the brand name "nil" in Go) is just crazy. Error handling is another strange thing in Go. And generics have been only introduced recently, but there is hardly any support for libraries in it (now). While Go is definitely fast enough for most scenarios, it is not the best…
> Creating a new language and repeating the "billion dollar mistake" by including null (sailing under the brand name "nil" in Go) is just crazy. Can you explain? What do I set ‘score’ to when someone hasn’t sat the test yet?
What's special is that it's not like Go/Java/JS/etc where *every* pointer/reference can be null, so you have to constantly be on guard for it.
If I give you a Thing in Rust, you know it's a Thing and can use it as a Thing. If I give you an Option then you know that it's either a Some or None.
If I give you a Thing in Go/Java/etc well, it could b nil. Java has Optionals...but even the Optional could be null...though it's a really really bad practice if it ever is...but it's technically *allowed* by the language. Rust doesn't allow such things and enforces it at the language and compiler level.