Rust: Programming a Guessing Game

[@matthewsorg656]

At 19:30, why do you need to move the let mut guess inside the loop? Shouldn't the io.stdin().readline(&mut guess) be reassigning guess? It's unclear to me why you need to reallocate guess every loop.

[@adityakadam024]

Is Mutable same as static in C/C++

[@adityakadam024]

whenever i open VS code from command prompt all my prior saved workspaces get deleted. I've to add them back to workspace like every time. this happens only in case of cargo.

[@JeremiKress]

Nice beginner friendly tutorial. Subscribed!

[@awdsqe123]

One little comment at 18:50, because of your excelent error handeling while parsing you wouldn't be able to close the program by typing a string, only by ctrl-c.

[@daanvanhove9657]

Thanks mate

[@mariopaesdealmeidajunior5375]

Great job!

[@許至宇]

What is the theme you applied to your VScode?

[@TheDevMethod]

I used Synth Wave ‘84

[@GlobalYoung7]

😊 thank you

[@DevonBagley]

Oh.. that's weird, I thought the title was Rust programming: A guessing game. I was like 😐 Glad I am not the only one that feels like programming rust is a guessing game. Just keep refactoring until it compiles, and your previously simple elegant implementation is a bloated mess of spaghetti.

[@oddmerlin9797]

Honestly that mostly stems from not being familiar enough. I felt the same using C and trying to deal with pointers and references. I’m learning rust now and I’m in the exact same boat again

[@DevonBagley]

@@oddmerlin9797 With the majority of my experience being weakly typed languages where every variable is basically a reference pointing to an arbitrary value keeping all of the information about types and ownership in mind requires a lot of additional mental energy because you are doing a lot of work that other languages would do for you at the expense of performance or memory waste.