My wife is taking Harvard's cs50 course to learn programming. In order to encourage her and to also practice my rust, I'm going to follow along and perform each week's challenge but in Rust.
I wanted to have all the weeks in the same repo, and to name the files similarly to cs50 so I avoided using cargo new
.
But that turned out to be dumb. Using cargo new --vcs=none name
turned out to be a much better way to avoid cargo trying to initialize git in an existing and superceding git repo. This way, VSCodium offered to link the Cargo.toml to my workspace settings in .vscode so that rust-analyzer would work automatically. Much better.
I'm still very new to programming. I work in IT, and sometimes I'll script something or write a little utility, but coding is not my day job. Therefore I have a decent understanding of core programming concepts, but very little real experience. I'm sure I'm making some poor choices as I write these. So feel free to open up an issue or PR to let me know of better ways, just be sure to explain why in small words.
These are the crates I used to complete challenges in some of the weeks' challenges.
Crate Name | Version | Week(s) Used | Description |
---|---|---|---|
cs50 | 1.0.1 | 1, 2 | A rust implementation of cs50.h from the cs50 class. |
rand | 0.8.5 | 2 | Used for psuedorandom functions |
colored | 2.0.4 | 2 | Used in Wordle50 to display colored backgrounds for the text. |