This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-11
Channels
- # adventofcode (31)
- # announcements (6)
- # babashka (5)
- # beginners (93)
- # calva (15)
- # cider (20)
- # cljs-dev (16)
- # clojure (159)
- # clojure-berlin (1)
- # clojure-dev (5)
- # clojure-europe (9)
- # clojure-italy (9)
- # clojure-losangeles (2)
- # clojure-nl (26)
- # clojure-spec (7)
- # clojure-uk (33)
- # clojurescript (54)
- # clojutre (5)
- # cursive (20)
- # datomic (23)
- # emacs (19)
- # events (1)
- # expound (1)
- # figwheel-main (1)
- # fulcro (104)
- # hyperfiddle (1)
- # jobs (1)
- # luminus (10)
- # malli (59)
- # nrepl (1)
- # off-topic (11)
- # pathom (5)
- # planck (15)
- # reagent (13)
- # reitit (8)
- # rewrite-clj (10)
- # ring-swagger (3)
- # shadow-cljs (129)
- # tools-deps (46)
- # xtdb (14)
- # yada (1)
Rough night after Ajax and a few beers
what did you write it on? π
https://github.com/transducer/adventofcode/blob/master/src/adventofcode/2019/day10.clj
Those are the answers to my input too
https://github.com/Average-user/adventofcode-clj-2019/blob/master/src/adventofcode_clj_2019/day11.clj
Until today I just used day5 code, modify it a little and so on, but I've decided to make intcode.clj
its own file ...
I'll do it tomorrow though
Add a couple of helper fns for extracting outputs and injecting inputs; honestly, may be worth converting fully to core.async
> Yeah, especially since he calls it 'complete' now
how do you mean?
The beginning of 9-2, in highlights: > You now have a complete Intcode computer. So the relative base + mode + instruction were the last pieces. From here on out, I expect if the Intcode computer is used, it'll be composed with some other system, e.g. the amplifiers and paintbot we've already seen.
loooool π
my part 2 text makes no sense
ah partition count error
still a bit magical to see the asciiart appear
cant wait to see the quill version from @fellshard
talk about synchronisity. Currently reading the joy of clojure. Just read: > To demonstrate this, let's build a robot object that has functions for moving it around a grid based on its current position and bearing.
Kind of hard to keep up with AoC on vacation . I canβt be bothered to refactor my code π . Iβm happy my core.async intcode solution works with n inputs, m outputs is any order https://gitlab.com/dmarjenburgh/adventofcode/blob/master/src/adventofcode/year_2019.clj#L254-275
Kind of hard to keep up with aoc during a work week π
Hmmm. I'm getting a "bad opcode" when I run part 1 on the real data, as it moves the PC (jumps) to a location whose value is not a valid opcode.
Nvm. Found it, was a lurking error in my input
opcode that just hadn't been triggered in a previous day.
I finally completed day 7 part 2 after finding out > All signals sent or received in this process will be between pairs of amplifiers except the very first signal and the very last signal. To start the process, a 0 signal is sent to amplifier A's input exactly once. didn't mean that the 0 signal should be sent before the phase signal πͺ
Such awesome puzzles π