AdventOfCode2019 VS aoc

The field is called "compiler design". Consider taking a course [1] or buying a book?

A somewhat more playful approach might be to complete the 2019 edition of Advent of Code [2], where you'll learn some preliminaries while implementing the Intcode interpreter.

[1] https://online.stanford.edu/courses/soe-ycscs1-compilers

[2] https://adventofcode.com/2019

The ending of Advent of Code 2019 was amazing. Well, the whole season was awesome, but the ending was amazing.

2019 in Rust

This is the seventh year puzzles, if you want to check out previous years take a look at: 2015, 2016, 2017, 2018, 2019, 2020

I believe this is the direct link to the mentioned challenges: https://adventofcode.com/2019

If you want to get started, I would recommend doing Advent of Code 2019 https://adventofcode.com/2019. It goes through and shows how to implement a basic VM. 0x10c / DCPU-16 is also a good place to start. Such simplified CPU-s help you get started and understand the basics without overwhelming you with the complexity :D.

Overall, I think this year felt a lot easier than the last one. Almost no graph problems, no path finding algorithms, and no insane math problems like day 22, 2019. It's really hard finding the right balance. I think 2019 was maybe a bit too hard and discouraged a lot of people. I like that this year was more approachable but perhaps it was a bit too easy towards the end.

Thanks for an amazing year! Definitely a lot easier this year than last one, which was a bit sad. No hard graph problems, requiring path finding algorithms, no insane math problems like day 22 last year. It's hard finding the right balance. I think 2019 was maybe a bit too hard and this year maybe too easy.

Personally I just stick to raw arrays for most days, usually with static storage (so pre-allocated). Keeps things simple! Here's my repo.

- C -

Here's my solution. Sorry, I did go a bit overboard making it compact.

That was one heck of a tough day but also very satisfying. I spent quite some time working out a 3D rectangle splitting/merging algorithm on paper and then I had to go and implement that in C. It turned out pretty clean and idiomatic, if I may say so!

This was my first attempt (or at least in a very long time) at generating video. Here I'm generating raw RGB frames in memory and writing them to ffmpeg, which works well enough but it's a little primitive.

At 50 year sold and very stable, C must be one of the easiest languages to get working on old machines. Required just some of the polyfills I wrote back in 2020.

My original solution checked every character against every other character, which performed perfectly fine even for 14 chars, but it felt wrong.

- C -

First a straightforward solution with a double buffer, later realised you could do it in-place by just holding onto one value per row/column.

First wrote a short AWK program to convert the input to C and play with it while running a hopeless brute force attempt.