Day 1: As I am just getting to know Rust, Rustlings has been my companion today and it delighted me with how soon tests were introduced. I am looking forward to making something in a strongly typed language for a change. #100DaysOfCode #rustlang
2
2
2
Day 3: I am so eager to stop dallying around and get to something real with Rust that I need your help to grow my patience, dear Rustaceans. What are the things devs coming from other languages most often misunderstand or underuse in Rust? #100DaysOfCode
1
5
3
Day 4: Today I realized I need some other approach to GUI than experimenting with Azul. Maybe I'll go with rust-sciter #100DaysOfCode #rustlang
1
3
3
Day 5: Having control of mutability and how borrowing and moving works will take some getting used to, but I do like the feel of it all. Still undecided about the GUI framework choice for my Linux app. #100DaysOfCode #rustlang
1
5
2
Day 6: Learned about error handling in Rust. Seems it fits my ways of thinking rather well! I also started experimenting with gtk-rs for the GUI though the choice is not yet carved in stone #100DaysOfCode
2
2
3
Day 7: I made yesterday optional and today all about Option. I took a look at the Rust community on Discord as well, but didn't interact much yet. It's humbling and refreshing to be a beginner again... I am itching to contribute or at least make something real πŸ˜€ #100DaysOfCode
2
3
2
I think I would like that, especially as I have often been a bit timid contributing and having someone help figure out the contribution policies and politics can make it all easier
1
I'll have a skim through the issues I've marked as being prepared to mentor and see if I can find a nice one for you
1
github.com/rust-lang/rustup/… might be a nice light one to get started with. It mostly involves improving an error message and perhaps the code which raises it. If that interests you then say so on the issue and we'll start the process. If not, say here and I'll look for another.

Jun 17, 2020 Β· 7:21 AM UTC

1