Day 11: Reactor

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

  • CameronDevOPM
    link
    fedilink
    arrow-up
    2
    ·
    1 month ago

    I also broke up the pathing, mine has zero paths from DAC to FFT. If I join DAC directly FFT, i get a stackoverflow, so maybe its intentional.

    • mykl@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 month ago

      Yes, it felt a little more like I was solving the puzzle-setter rather than the puzzle today.

    • EnEnCode
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      If you can explain why it works, not calculating half the paths isn’t a hack—it’s an optimization. ;)

      • CameronDevOPM
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        I think the hack was just skipping the entire second set of paths, but yeah, splitting was an nice optimisation. Might not scale as well if that path had to hit multiple intermediate nodes though.