ps. look out for all my other solutions for Advent of Code challenges here.
See details of the challenge here.
Today’s input looks like this:
cpy a b
cpy a d
cpy 0 a
cpy b c
Today’s challenge is an extension to Day 12, where we have introduced a new instruction for toggle (tgl). To make toggling logic simpler let’s introduce a union type to represent the different instructions we can receive and write a function parse them.
Next, let’s add a toggle function to toggle a given instruction and modify the execute function from Day 12 to work with the union type and support the new tgl instruction as well.
Now we can solve part 1.
let part1 = (execute [ “a”, 7 ] inputs).[“a”]
The safe doesn’t open, but it does make several angry noises to express its frustration.
You’re quite sure your logic is working correctly, so the only other thing is… you check the painting again. As it turns out, colored eggs are still eggs. Now you count
As you run the program with this new input, the prototype computer begins to overheat. You wonder what’s taking so long, and whether the lack of any instruction more powerful than “add one” has anything to do with it. Don’t bunnies usually multiply?
Anyway, what value should actually be sent to the safe?
As the description eludes to, if we use 12 as initial input it might take a while to run.. and the naive approach of just executing the logic as before, ie
let part2 = (execute [ “a”, 12 ] inputs).[“a”]
took a good 4 minutes to run on my 2015 MBP.
If you add a few printfn statements and you’ll a few blocks of instructions that repeat for many cycles, eg.
cpy b c
jnz c -2
jnz d -5
you can add a short-circuit when you see this happen and replace it with the equivalent of a = b * d (as the description eluded to).
- Day 23 challenge description
- Advent of Code 2015
- Solution for Day 22
- Solution for Day 12
- All my F# solutions for Advent of Code
- Github repo
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.
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.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong