Learning Rust from Zero

tutorials
21

Cool ! Thanks for sharing !

22

I’m a complete beginner, I’ve never written a single line of code in any language. I decided to learn Rust for a project of mine, and this post is incredibly useful for getting started. It might not be perfect or fully comprehensive for a novice, but everyone has to start somewhere, and you learn as you go.

Thanks a lot for this post!!

23

Glad it helps :slight_smile:

24

Hey, that's a great job, thank you.

25

Thanks! I wonder how far did y'all go because I understand it's very hard to go through the last several chapters :laughing:

26

You can leave your book on Wikibooks :slightly_smiling_face::graduation_cap::books: for I will can read it from Kiwix offline if we will have here some issues with the Internet connection :electric_plug::slightly_smiling_face:

If you want it :grin:. There's a ton of other literature, btw! :slightly_smiling_face::+1:

27

And, yeap :thinking:, I obviously know, that I can download it as a PDF separately :man_shrugging:

28

Not sure if it's a good idea to put an AI-assisted tutorial on Wikibooks though. Even if it's fine I would like to gather more feedback first

29

When I downloaded the PDF my PDF-reader shown me that there's 614 pages :man_shrugging:

30

It's possible that you're right :thinking:

I just tried to read your book :green_book: by a quick-look :nerd_face: just now, and there was be some moments those I was can't understand immediately, but then I understood them. But they still may confuses sometimes (but, at least, just in my case)

1.5.2.4 Using Multiple {}s

First thing that I though is that... If I will put s after {} then I will do something different? :sweat_smile: And it was seems in my mind somehow like that then :slightly_smiling_face::

fn main() {
  let a = 10;
  let b = 3;
  println!("{}s + {}s = {}s", a, b, a + b);
}

You will need to understand that my English is still not pretty nice, but... Again! :slightly_smiling_face: Then I understood what is it here talking about :grin:

And... Those {}s is okay? :thinking: Or this is an AI "hallucinations"? :slightly_smiling_face:

31

He was referring to an mdbook-native print version, which I removed for some reason (plus I don't think it's still needed when we already have the source code and the PDF version)

32

The 's' here is merely referring to plurality. It's like saying fns in Rust. If the inline code section is rendered better it can help. Not sure if it's worth to change the CSS for this specific issue

Edit: Oh I see you're reading the PDF version. Let me take a look.

33

Ohhh... :thinking: Okay :ok_hand:. I just can't remind that I met something like this before :thinking:. For example, in those books on Wikibooks :books: those I read before :thinking:

P.S: Yeap! In the PDF version is exactly that what we are talking about now :slightly_smiling_face:. The same, and nothing different :grin:

34

Would it be better to say "pairs of curly braces" instead of {}s? I have to admit I'm a bit reluctant to fix this :rofl:

35

Maybe just {}? :thinking: Without any s at the ends? :thinking: Because, I guess, word Multiple is enough here :slightly_smiling_face:

36

But... Okay :thinking:... I may be wrong here :slightly_smiling_face:

37

Nevermind! :slightly_smiling_face: I thinks that they're just tiny things those we don't need to pay attention to :grin:

Thanks for your contribution to the Rust :crab: community, for your efforts :slightly_smiling_face::handshake:, I really want to think that this book was be made by human (at least, mostly) :grin:, and just for the nice book :green_book: that may be useful and interesting for some bodies :slightly_smiling_face: (even, maybe for me. But I'll need to check it out :grin:)

P.S:

interesting for some bodies :slightly_smiling_face:

I meant :thinking:, for the most people who have an interest in Rust :crab: :slightly_smiling_face:

38

I took a look at the book, and I must say I am impressed. From the few pages I read, it seems high-quality and accurate.

Furthermore, I'm not a fan, personally, of LLMs, but this is a rare example of a quality piece being made, rather than prompt-and-go, non-reviewed slop.

One criticism, however, is the almost obscene level of detail. The Rust Book is made for somewhat more experienced programmers, yet focuses less on documenting every single thing, and more on thoroughly showcasing the most useful pieces of kit. Overwhelming new users, and especially new programmers, is maybe not a good idea, and one of the best parts of learning a new language is discovering new things oneself.

Overall, though, a good publication. Well done.