summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2022-12-25reorder tests in day25HEADmainMartin Ashby
2022-12-25day25pt1Martin Ashby
2022-12-23day18 pt2Martin Ashby
2022-12-22day18 pt1Martin Ashby
2022-12-18day17Martin Ashby
Found an approach I think will work
2022-12-18day17 pt2Martin Ashby
But it's the wrong track, it's too slow.
2022-12-18day17 pt1Martin Ashby
2022-12-17day17 skeleton...Martin Ashby
2022-12-17day16 pt2Martin Ashby
2022-12-17day16 part 1Martin Ashby
2022-12-16Remove loggingMartin Ashby
2022-12-16Be less clever. Simply iterate through y valuesMartin Ashby
But instead of straightforwardly iterating x, jump to the end of the containing line segment to skip a lot of values Also then cheat :p
2022-12-16day15 pt1Martin Ashby
2022-12-15day14Martin Ashby
2022-12-13day13Martin Ashby
2022-12-12day12Martin Ashby
2022-12-11day11Martin Ashby
This one took a lot longer than I'd like!
2022-12-10day10Martin Ashby
2022-12-09day9Martin Ashby
2022-12-09day8Martin Ashby
2022-12-07day7Martin Ashby
This one was a little trickier, as the obvious solution for navigating back up a tree is to keep a reference to the parent. However that's essentially a doubly linked list which is a pain in the ass in Rust. Instead, use a separate variable for the current 'key' into the tree I'm not especially happy with the terminal processing as well, since after the 'ls' command we need to 'peek' at the next entry to see if the 'ls' has finished and we're onto a next command I couldn't think of a very good way to do this except loops and loops.
2022-12-06Day 6Martin Ashby
Reasonably simple this one :)
2022-12-05Remove extraneous prints from day5Martin Ashby
2022-12-05day5Martin Ashby
Not super happy with this, fell back to iterative programming pretty heavily (: Also a ton of .unwrap(), but this is an artifical problem not a real world
2022-12-04day4Martin Ashby
2022-12-03Tidy up day 3Martin Ashby
2022-12-03Days 1-3Martin Ashby