Skip to content

wrightdylan/advent-of-code-2022

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

🎁🎄 Advent of Code 2022 (Refactored) 🎄✨

These are my solutions to this year's Advent of Code, which will be attempted in the Rust programming language, which I am still in the process of learning. I only just found out about this a couple of months ago!

Note: I am currently refactoring to make use of cargo-aoc code helper (here), and completing missing puzzles. Times that show 'xxxxxx' are not complete yet.

Solutions

All solutions linked below:

Day Title 1 ⭐ 2 ⭐ Solution Rating
01 Calorie Counting 436ns 10.8µs day01.rs 😃
02 Rock Paper Scissors 32.6µs 30.4µs day02.rs 🤔
03 Rucksack Reorganisation 53.1µs 68.4µs day03.rs 😁
04 Camp Cleanup 406µs 74.7µs day04.rs 😄
05 Supply Stacks 14.8µs 23.5µs day05.rs 😭:goberserk:
06 Tuning Trouble 203µs 1.37µs day06.rs 🤗
07 No Space Left On Device 343ns 732ns day07.rs 😓😩
08 Treetop Tree House 342µs 483µs day08.rs 😖
09 Rope Bridge xxxxxx xxxxxx day09.rs ⌛📷
10 Cathode-Ray Tube xxxxxx xxxxxx day10.rs ☺️😌
15 Beacon Exclusion Zone xxxxxx xxxxxx day15.rs 🤔🧐
16 Proboscidea Volcanium xxxxxx xxxxxx day16.rs 🥾🚶
18 Boiling Boulders xxxxxx xxxxxx day18.rs 🌞📷
19 Not Enough Minerals xxxxxx xxxxxx day19.rs 🤷‍♂️

Notes

  1. Now that I have a better understanding of how this event is run, I may start uploading single file solutions from this point on, but I may still keep them split so I can have separate comments for both parts. Instead what I'll do is refactor part B to give answers to both parts where I can. Instances of part B that do not combine both answers will have a lighter background.
  2. Day 05 was torture because of that parsing. Clearly something to work on. This meme was me.
  3. Day 08 - a little point to bear in mind for future puzzles: be sure to read the example very carefully 🤦‍♂️. You can save a lot of time that way, instead of wondering why the code isn't working ☠️.
  4. Some days I just don't have the time ⌛.
  5. Day 15b could have been completed on time, but I really didn't want to brute force this but instead look for a more elegant solution. I've figured one out, but I will have to come back to that another time since Day 16 has been released.
  6. Day 18 was such a beautiful day, the first time this month. It seemed like a real waste not to go out all day.
  7. Week three is getting hard. It's reassuring to know devs with decades of exerience have found week 2 hard. I can say that I have learned a lot so far, and reading discussions I have also come away with a couple good book recommendations for algorithms, and other concepts such as dynamic programming.
  8. Having finished AoC 2023, I've come back to this to refactor, and complete missing puzzles.
  9. Day 5's parser is still awful even after refactoring (but not as bad as the original).