Day 5: Cafeteria

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
[โ€“] [S] 1 point 10 months ago (1 child)

That is nice and simple, power of python I guess. How quick was the pt2 solve? I could imagine that being pathalogically slow with the wrong ordering of inputs?

Eg: (99,100),(0,1),..., (95,96), (96,97), (97,98), (98,99)

  • source
  • parent
  • hideshow 1 child comment
  • [โ€“] 2 points 10 months ago* (last edited 10 months ago)

    I haven't timed it, but easily below a second.
    Could that be optimised? Most certainly.

    Due to the ranges being in a set, rather than a list, the input order doesn't matter anyway. And the set really does a lot of heavy lifting for making the code so concise. You'll need a bunch of boilerplate for list maintenance, especially if you continuously keep it sorted.
    The set also removed 8 duplicates I had in the input.

  • source
  • parent