It is only going to be downhill from here

  • Deebster@programming.dev
    0·
    10 months ago

    I can’t code today because of travel, just as the one that might run slow enough to geek out on benchmarking the various options. Does seem like it’s a bit of a jump in difficulty from previous days.

    • CameronDev@programming.devM
      0·
      10 months ago

      Based on the slow trickle of results pt2 was very hard. But, having now got a good result, its not that difficult, but getting to that solution/algorithm took a lot of brain power.

      I hope todays is a little bit more relaxed.

  • NominatedNemesis@reddthat.com
    0·
    10 months ago

    It was easy staight forward brtue force:

    Spoiler 
    For each possible_rectange Find Max:
   If polygon.contains(rectangle) Then rectangle.area() Else 0

    For speed the loop can be run paralelley.

    I had no time to implent the contains myself, but pretty much all languages have a library already.

    • Avicenna@programming.devOP
      0·
      10 months ago

      yea becomes trivial if one uses a polygon library (I did too) but looking at the actual polygon, one can cook up some clever heuristics to do it quite quickly with some basic checks I think.