Advent of Code F# – Day 9

Yan Cui

I help clients go faster for less using serverless technologies.

Table of Content

This article is brought to you by

Is your CI build step taking too long? Try Depot for free today and experience up to 40x faster build speed!

Unlock faster CI for FREE

ps. look out for all my other solutions for Advent of Code challenges here.


Day 9

See details of the challenge here.

The input for today’s challenge is a very long string like this:


First, let’s see how we’re gonna parse this input.

The approach I went with is to recursively split the input with input.Split([| ‘(‘; ‘)’ |], 3) which will return either:

  • the whole string if there’s no (n x count) section, eg. “ADVENT” => “ADVENT”
  • or an array of 3 elements
    • for “X(1×3)YZUVW”, it’ll return [| “X”; “1×3”; “YZUVW” |]
    • for “(1×3)YZUVW”, it’ll return [| “”; “1×3”; “YZUVW” |]

To parse the number of characters (n) and number of times to repeat (count) from “1×3” we can introduce an active pattern (the Repeat pattern below) to do the job.

Now we can recursively split the string and count the length of the decompressed string.


Part 2

Apparently, the file actually uses version two of the format.

In version two, the only difference is that markers within decompressed data are
decompressed. This, the documentation explains, provides much more substantial
compression capabilities, allowing many-gigabyte files to be stored in only a
few kilobytes.

For example:

(3×3)XYZ still becomes XYZXYZXYZ, as the decompressed section contains no
X(8×2)(3×3)ABCY becomes XABCABCABCABCABCABCY, because the decompressed data from
the (8×2) marker is then further decompressed, thus triggering the (3×3) marker
twice for a total of six ABC sequences.
(27×12)(20×12)(13×14)(7×10)(1×12)A decompresses into a string of A repeated
241920 times.
(25×3)(3×3)ABC(2×3)XY(5×2)PQRSTX(18×9)(3×2)TWO(5×7)SEVEN becomes 445 characters
Unfortunately, the computer you brought probably doesn’t have enough memory to
actually decompress the file; you’ll have to come up with another way to get its
decompressed length.

What is the decompressed length of the file using this improved format?

Part 2 requires slightly more work and, as the challenge hinted, we might overflow on int so let’s use int64 instead.

The main difference to part 1 is that we need to make the decompressV2 function itself recursive, and call into it from inside the loop function to work out the decompressed length of the repeated section.



Whenever you’re ready, here are 4 ways I can help you:

  1. Production-Ready Serverless: Join 20+ AWS Heroes & Community Builders and 1000+ other students in levelling up your serverless game. This is your one-stop shop for quickly levelling up your serverless skills.
  2. Do you want to know how to test serverless architectures with a fast dev & test loop? Check out my latest course, Testing Serverless Architectures and learn the smart way to test serverless.
  3. I help clients launch product ideas, improve their development processes and upskill their teams. If you’d like to work together, then let’s get in touch.
  4. Join my community on Discord, ask questions, and join the discussion on all things AWS and Serverless.

Leave a Comment

Your email address will not be published. Required fields are marked *