25
๐Ÿ’ƒ - 2025 DAY 3 SOLUTIONS - ๐Ÿ’ƒ (programming.dev)
submitted 9 months ago by [M] to c/advent_of_code@programming.dev
33 comments fedilink hide all child comments
 

Day 3: Lobby

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

you are viewing a single comment's thread
view the rest of the comments
[โ€“] 2 points 9 months ago (3 children)

Nice! I thought about using numbers but then decided that strings are a lot easier to deal with.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [โ€“] 1 point 9 months ago (2 children)

    I was curious, so I ran yours and it is only like 3-4ms slower. I was honestly surprised it was that close.

    Just goes to show that we're often wrong when estimating and the only real way to know is to benchmark.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 2 points 9 months ago

    My version used strings as well, and I thought that as I was comparing small integers either way, it made sense to stay in ASCII as the strings were already easy to index, and it meant I could skip parsing input numbers, only needing to parse output numbers so they could be summed.

    I did start with numbers so I could convert it back to compare, but it's so fast (the whole thing takes 1ms - and that's reading/parsing the input twice) that it's almost a micro benchmark.

  • permalink
  • fedilink
  • source
  • parent