Description for today’s challenge is here.
It’s the last day of the advent calendar, and today’s challenge appears difficult at first but mostly because of the grid system it imposes upon you.
But after some thought, the problem can be drastically simplified.
Given this grid system:
we can work out the one-based index for row N, column 1 in this formula:
F N = F(N-1) + (N-1) where F 1 = 1, F 2 = 2
F 2 = 2,
F 3 = F 2 + (3 – 1) = 2 + 2 = 4
F 4 = F 3 + (4 – 1) = 4 + 3 = 7
From here, column M is (M – 1) distance away from the first element on the same row and (M – 1) distance away from the row N that marks the start of the diagonal:
So, the one-based index for row N, column M can be expressed in terms of the F function above:
G (M, N) = F (N + M – 1) + (M – 1)
G (3, 2) = F (2 + 3 – 1) + (3 – 1) = F 4 + 2 = 7 + 2 = 9
G (6, 1) = F (1 + 6 – 1) + (6 – 1) = F 6 + 5 = 16 + 5 = 21
So for my puzzle input of row 2981, column 3075, it translates = G (3075, 2981)th element where the first element is 20151125.
Taking all these into account, and translating G (M, N) into an (x, y) based system, we can have the following to solve today’s challenge:
Pretty straightforward, right? Well, the only caveat is how we implemented F here, this is only because I wanted the implementation to be tail recursive, otherwise it can be simple as:
let F = function | 1 -> 1 | 2 -> 2 | n -> F (n-1) + (n-1)
So that’s it folks! We’ve completed all the Advent of Code challenges for 2015, and our F# xmas tree is up and running in all its glory
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
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