6 ms·
Best advent of code I’ve done was the ”int-code computer” one. So good - one recurring theme of making a computer and in the end running games on it! Super exc
by Torkel 5y ago
Best advent of code I’ve done was the ”int-code computer” one. So good - one recurring theme of making a computer and in the end running games on it!
Super excited for this year’s edition :)
- wodenokoto 5y agoHaving never written anything close to a parser or a compiler, I totally crashed on that one. I often misunderstood subtleties in the problem formulation and had to read solutions in order to figure out the question and ended up with such a mess of if-else statements for compiling int-codes that it just became impossible to extend my program.
- nikanj 5y agoBut now you have written one, which might come in handy at some point in your career.
- wodenokoto 5y agoWell, I guess I know now how not to write one ;)
- wbc 5y agoway to sum up my coding career :D
- breckenedge 5y agoI agree. That year was the only one in which I completed all of the puzzles the day they came out.
- viceroyalbean 5y agoOne of my favorite things about the intcode computer was implementing the extendable memory by just appending an infinite list of zeros using haskell's lazy evaluation. Unfortunately my implementation was incredibly slow (probably because of the linked lists) and I only made it about halfway through.
- gameswithgo 5y agomy fun thing was running my intcode computers in parallel
- CornCobs 5y agoI also did that year in haskell! My favorite part was using knot tying to feed the output of my intcode machine into itself! Lazy evaluation allowed me to continue expressing my intcode machine as a pure function of [Int] -> [Int] without having to restructure the entire machine to allow getting an output, then adding the next input to the machine in a step-wise manner usually accomplished with generators of some sort in other languages
- 1-more 5y agoWas this 2019? I did half of it in elm. Simulating a processor with the core states of read, eval, and write was very cool. Using setTimeout to send it clock signals was very slow until I realized I could compose the processor step function to run a few thousand clock cycles per timeout. Wild time.
- dunham 5y agoThat was my first and my favorite so far. I did it in Haskell, barely knowing Haskell, which made things a bit interesting. I ended up learning/using STArray for the memory.
- a20eac1d 5y agoThat sounds amazing, is there any way to access this material right now?
- NLips 5y agoYou can see any year by changing the url: https://adventofcode.com/2021 https://adventofcode.com/2021 I think it started in 2015. On the AoC website you need to provide solutions for each day in a given year to see the next day’s problem, so you can’t instantly see all the problems from a given year unless you’ve previously completed them. You may be able to find the problems elsewhere on the net.
- forgotpwd16 5y agoAll problems are available as long as their day has come even while the event is running. But the part 2 of each problem requires solving part 1 first.
- NLips 5y agoHah - I’ve assumed for years that days weren’t accessible because the section of ASCII art for them is greyed out!
- wodenokoto 5y agoyou write the intcode computer in AoC 2019 https://adventofcode.com/2019 https://adventofcode.com/2019 Not everyday is about intcodes, but day 2, 5 and 7 are the first 3 days with intcodes and they built on top of eachother.
- guavaNinja 5y agoHere is one for 2019 https://adventofcode.com/2019/day/2 https://adventofcode.com/2019/day/2