Advent of Code F# – Day 16

(this post is part of the F# Advent Calendar project, check out all the other great posts there! And special thanks to Sergey Tihon for organizing this!)

The source code for this post (both Part 1 and Part 2) is available here and you can click here to see my solutions for the other Advent of Code challenges.

Description for today’s challenge is here.

 

Day 16

The input for today’s challenge looks like this:

Sue 1: goldfish: 6, trees: 9, akitas: 0

Sue 2: goldfish: 7, trees: 1, akitas: 0

Sue 3: cars: 10, akitas: 6, perfumes: 7

Sue 4: perfumes: 2, vizslas: 0, cars: 6

so to make parsing a little easier, I decided to use Regex with a bit of help from an active pattern:

day16_01

and we also need a type to represent what we remember about each Aunt Sue. (ok, we don’t strictly need one, a tuple can also do the trick, but as we’ll be passing the payload around I think it’s a lightweight record would be easier to work with in this case )

day16_02

For each line in the input:

Sue 1: goldfish: 6, trees: 9, akitas: 0

we need to fetch the number, and a key-value pair for each of the things we remember about that particular Aunt Sue. Something along the lines of:

day16_03

Now, we have all the information we can remember about all 500 Aunt Sue’s, as well as the facts our My First Crime Scene Analysis Machine has told us about the Aunt Sue that we need to send a thank you card for:

day16_04

Finally, we just need to go through all the Aunt Sue’s, and find the one that matches up with the facts.

As the requirement specified,

Things missing from your list aren’t zero – you simply don’t remember the value.

so if we can’t find a given key (from the list of facts) in the things we remember about an Aunt Sue we should just presume it to be true:

day16_05

 

Day 16 (Part 2)

Oh, what shock horror, that we managed to misread the machine’s output! Luckily, our code is written in F# and pattern matching makes the required change a piece of cake 

Since the new requirements are:

the cats and trees readings indicates that there are greater than that many, while the pomeranians and goldfish readings indicate that there are fewer than that many…

so we just need to tweak our logic slightly with additional match cases to cater for those two special cases:

day16_06

and job done! F# saves the day and Aunt Sue gets her thank you card! ho ho ho 

Liked this article? Support me on Patreon and get direct help from me via a private Slack channel or 1-2-1 mentoring.
Subscribe to my newsletter


Hi, I’m Yan. I’m an AWS Serverless Hero and the author of Production-Ready Serverless.

I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.

Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.

Hire me.


Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.

Get Your Copy