Day 9: Disk Fragmenter

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

  • CameronDev@programming.devOPM
    link
    fedilink
    arrow-up
    1
    ·
    18 days ago

    You coded this on a phone, with a touchscreen keyboard? Not sure who is more impressive, you or the unicode wizard :D

    • Deebster@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 days ago

      I just ran this on a laptop - it worked (part one only) but took 4h28m21s so Nushell is not a language for AoC (or I just coded it very poorly).

        • Deebster@programming.dev
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 days ago

          One core was busier, but it wasn’t at 100%. My Rust code yesterday was the same, perhaps it’s taking too much time accessing memory.

          The time was wall time (as per Starship’s output) but it was still waaay too slow to bother with again!

    • Deebster@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      18 days ago

      Haha, thanks but we both know they’re #1 by a country mile. I think my phone’s now downclocking as it’s burning up and still hasn’t spat out an answer after two hours, so I technically haven’t completed it yet!

      Edit: Calling it for now, I might figure out later why it’s so slow (there’s some easy but minor gains to be made but I’m guessing there’s some O(awful) going on that the input’s blown up)