7495f9e378
Still non-working part 2. But I have an idea.
chrisly422025-12-10 21:43:08 +01:00
ccc3fdad4c
Restored deleted code from previous commit and used it to solve Part 1 much faster.
chrisly422025-12-10 18:44:40 +01:00
bd591263f6
Still not working, but stuff removed that was wrong.
chrisly422025-12-10 17:02:28 +01:00
4982f2cb3c
Non working solution before I re-read the instructions regarding the light diagrams to be ignored for part 2.
chrisly422025-12-10 16:54:58 +01:00
6299b10b85
Day 10. Part 2 doesn't terminate in time and space yet.
chrisly422025-12-10 07:44:08 +01:00
caf82dd7a9
Restored "clever" method for day 9. Not much faster, though.
Chris Hodges2025-12-09 13:06:28 +01:00
d2044f2d6a
Day 9. Removed all smart code.
chrisly422025-12-09 08:36:22 +01:00
9a2a22805b
Day 9. Tried to be smart, that was a failure.
chrisly422025-12-09 08:34:40 +01:00
909fb5c7d2
Day 8: Use long for result of part 2. X coords are > 16 bit. That it didn't overflow was pure chance.
chrisly422025-12-08 07:07:39 +01:00
26661cbfd8
Minor fixes to readme and user agent.
chrisly422024-12-08 13:07:05 +01:00
8cdfdda1f4
Removed all puzzle descriptions, replaced by a link. Not deleting history though: People who want to get the descriptions will do so anyhow.
chrisly422024-12-08 12:54:38 +01:00
0876e5c92c
Refactored CharGrid class to use a generator instead of two for-loops. Deprecated old API.
chrisly422024-12-08 08:05:40 +01:00
9d61ce1bc4
Day 8. Could have been faster if I think first.
chrisly422024-12-08 07:14:18 +01:00
15ce1ad06e
Day 7 Part 2 best brute force optimization without using dynamic programming.
chrisly422024-12-07 07:20:08 +01:00
8d492486fb
Day 7 Part 2 optimized to 666ms (instead of around 3000ms).
chrisly422024-12-07 07:13:32 +01:00
3cc10ea7c3
Day 6, can't seem to get part 2 working :-(
chrisly422024-12-06 07:41:33 +01:00
a14958b8a6
Day 5, total failure, mainly due to testInput containing extra lines without me noticing. Stopping this madness once and for all.
chrisly422024-12-05 07:24:28 +01:00
7695a005c9
Day 3, meh for having multiple lines of input and meh for having two different inputs and meh for being lazy.
chrisly422024-12-03 06:23:12 +01:00
6b27f3741d
Was bored, so started to do 2015.
chrisly422023-12-28 20:01:40 +01:00
73164a0ee3
Unlike other people, I don't have a ready set of graph algorithms ready, so I tried a bit to implement Karger, before I went back and simply added -Kneato to my dot graph output and then the edges to cut became very clearly visible. I could have saved a couple of hours.
chrisly422023-12-25 08:10:42 +01:00
0acad0121c
Day 24. This was a mad thing. I hate you all for using term solving tools under python. Thanks to the other kotlin guy who went the chinese remainder path and give a good amount of inspiration (strangely, the test input fails). I was thinking that some sort of modulo arithmetic could solve it, but it was too hard to figure out. What a waste of an otherwise nice xmas day.
chrisly422023-12-24 14:50:09 +01:00
6b904bb42c
Minor optimization on speed for day 23.
chrisly422023-12-23 12:40:51 +01:00
3a8a2d79a9
Minor update to Day 15 because I should have used a linked hashmap in the first place, if I had only read the instructions clearly enough.
chrisly422023-12-16 13:19:03 +01:00
chrisly42
Chris Hodges