✨ New series: Advent of Code 2022 ❄️
A pretty long Day 1, wherein we go over #rust types, traits, iterators... to bear's chagrin. Then we come up with a ridiculous solution, because of course we do.
https://fasterthanli.me/series/advent-of-code-2022/part-1 #xp
☃️ Advent of Code 2022, Day 2 🌲
In this one, we make our own enum and struct #rust types to model the problem accurately. And then.. more iterator shenanigans, including dealing with fallible iteration.
https://fasterthanli.me/series/advent-of-code-2022/part-2 #xp
✨ Advent of Code 2022, Day 3
In which we learn about immutable data structure in #rust, and more iterator tricks!
https://fasterthanli.me/series/advent-of-code-2022/part-3 #xp
🧑🎄 Advent of Code 2022, Day 4
...is a short one. But I went ahead and added some reader suggestions to Day 1 and 3, check them out!
We still have time to learn about extensions traits in #rust, don't worry: https://fasterthanli.me/series/advent-of-code-2022/part-4 #xp
📦 Advent of Code 2022, Day 5
In that one, we finally get to use the nom crate to write proper parsers.
We also learn how to work around the #rust borrow checker, and, just to see if we can, we chase down heap allocations!
https://fasterthanli.me/series/advent-of-code-2022/part-5 #xp
@fasterthanlime Interesting hearing about different parser options. How did you like using nom?
I'm new to #rust but ended up using the Recap crate https://crates.io/crates/recap. Seemed like an elegant solution. Curious your thoughts.
@haruska I like nom a lot, Geoffroy did good work there :) I've been using it in other contexts (HTTP, etc.)