Just committed my day7 solution
alvises
NobbZ
I finished a couple of minutes ago.
Part1 was quite easy to solve and didn’t require any changes to the VM code itself.
For Part2 I hacked some send/receive mechanics into it, but its quite ugly and I will probably refactor the machine at some point in time to always run as a named process.
- Day7 module: lib/y2019/d7.ex · master · Norbert Melzer / aoc_ex · GitLab
- changed IntcodeVM: lib/y2019/intcode_vm.ex · master · Norbert Melzer / aoc_ex · GitLab
1
cblavier
A few hours later, just made another pass of refactoring on my code.
It’s much more easy to understand now (I think 
)
0
aaronnamba
I rarely revise my AoC solutions after the fact, but today I did, to learn how to use processes and messages.
Unsurprisingly, it turned out to be a cleaner, albeit slightly more complex solution: fewer LoC and less data being slung around, but more moving parts → more failure modes.
Somewhat surprisingly, it required very minimal changes to my existing interpreter code (the main reason I didn’t do it this way from the start).
0
JEG2
Author of Designing Elixir Systems with OTP
ferd
Author of Property-Based Testing with PropEr, LYSE, & Erlang in Anger
Day 7 frustrated me a ton with the definition of the second problem. It was not very difficult to get it to work (I went with the approach where input/output are done through message passing and running the evaluators in parallel), but it was very challenging for me to figure out the execution model they wanted and where the output was supposed to land:
2