I've only ever used GCed (and largely dynamic) languages up until now (Python, JS and Clojure primarily); C is alien and C++ is frankly terrifying. With all that, I've been having a ball using Rust to solve Project Euler problems, with astonishing speed compared to what I'm used to. It doesn't quite have all the libs you might want for general development yet, but for the things it's currently equipped for it's a lot…
I would looooove any insight that you have on making the docs better for people who haven't done systems programming before. If you've ever got the time to type out a few thoughts, my email is in my profile.
A 30-minute Introduction to Rust
81–90 of 94 posts
Re: A 30-minute Introduction to Rust
#82Out of curiosity I implemented the two examples in C++11. For the number add I used a unique_ptr (although returning by value would be better in every way). For the shared state I used async with a lamba that calls transform and returns the modified vector through a future. This doesn't execute in parallel for each for loop though. I think something like Arc can be coded in C++ too - template wrapper that returns a R…
> Right now the extra compile-safety of Rust is IMO not worth giving up the other benefits of C++ I can't speak to everyone's use case, but for ours memory safety is extremely important. C++ is not safe, and we still see tons of memory safety issues, many security-sensitive, in practice, despite using modern C++ for all new code. Even if safety isn't as important to you, there are other reasons you might be intereste…
What are concepts in this context? It is hard to google.
Re: A 30-minute Introduction to Rust
#83I've only ever used GCed (and largely dynamic) languages up until now (Python, JS and Clojure primarily); C is alien and C++ is frankly terrifying. With all that, I've been having a ball using Rust to solve Project Euler problems, with astonishing speed compared to what I'm used to. It doesn't quite have all the libs you might want for general development yet, but for the things it's currently equipped for it's a lot…
I would looooove any insight that you have on making the docs better for people who haven't done systems programming before. If you've ever got the time to type out a few thoughts, my email is in my profile.
On the other hand, the writing style is way too "cute". It is legitimately distracting to see all these "Hooray!" and "Wait, whaaaat?" and "Not too shabby! I love eliminating mutable state.". It's unhelpful at absolute best.
Otherwise - thank you very much for this. Your docs are undeniably crucial for the adoption of Rust and they're extremely helpful.
Re: A 30-minute Introduction to Rust
#84Earlier quoted context omitted.
I would looooove any insight that you have on making the docs better for people who haven't done systems programming before. If you've ever got the time to type out a few thoughts, my email is in my profile.
The docs are great, and the fact that numerous examples with line-by-line explanations are coupled with higher-level prescriptions makes the docs great. Often documentation is too formal, and this formality makes it difficult to follow. On the other hand, the writing style is way too "cute". It is legitimately distracting to see all these "Hooray!" and "Wait, whaaaat?" and "Not too shabby! I love eliminating mutable…
And you'll be happy to hear my contract includes examples for _everything_ in the stdlib, so get ready for more of those!
Re: A 30-minute Introduction to Rust
#85Earlier quoted context omitted.
I would looooove any insight that you have on making the docs better for people who haven't done systems programming before. If you've ever got the time to type out a few thoughts, my email is in my profile.
Maybe you could make a survey that people who read these tutorials/guides/introductions could take after reading them?
Re: A 30-minute Introduction to Rust
#86Earlier quoted context omitted.
> Right now the extra compile-safety of Rust is IMO not worth giving up the other benefits of C++ I can't speak to everyone's use case, but for ours memory safety is extremely important. C++ is not safe, and we still see tons of memory safety issues, many security-sensitive, in practice, despite using modern C++ for all new code. Even if safety isn't as important to you, there are other reasons you might be intereste…
> concepts What are concepts in this context? It is hard to google.
Re: A 30-minute Introduction to Rust
#87Re: A 30-minute Introduction to Rust
#88Earlier quoted context omitted.
http://en.wikipedia.org/wiki/Concepts_%28C%2B%2B%29
Is this something that can be used in Rust? Or is it a feature that will be implemented later?
I've pinged #rust, I'll see if I can get someone who knows more to answer here.
Re: A 30-minute Introduction to Rust
#89Earlier quoted context omitted.
The docs are great, and the fact that numerous examples with line-by-line explanations are coupled with higher-level prescriptions makes the docs great. Often documentation is too formal, and this formality makes it difficult to follow. On the other hand, the writing style is way too "cute". It is legitimately distracting to see all these "Hooray!" and "Wait, whaaaat?" and "Not too shabby! I love eliminating mutable…
Thanks. Yeah, I specifically have a thing open for it being too much in my own voice. Since this was basically ported wholesale off of my blog, it was better there... And you'll be happy to hear my contract includes examples for _everything_ in the stdlib, so get ready for more of those!