Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Advent of Code 2023 is nigh

adventofcode.com

Post reply on HN
Print view View original

181–190 of 319 posts

Re: Advent of Code 2023 is nigh

#181

Post by dgacmu »

63 wrote: post #76

Day one part 2 was relatively rough. Things I learned from it: rust regex crate doesn't support look-ahead, rust onig crate is currently broken in many ways and shouldn't be used (the version in crates.io doesn't compile and the version on GitHub is failing tests and look-ahead isn't working). It was a very frustrating time for me. After 2 hours of troubleshooting the above I used the same approach in python and it t…

You might try BurntSushi's aho-corasick crate. It led to a fairly nice solution in Rust for this one. (It will report overlapping matches)

Re: Advent of Code 2023 is nigh

#182

Post by hypersoar »

shever73 wrote: post #92

As others have said, part 2 of today's was really difficult. I finally solved it using Python regex `overlapped=true`, but it was very tricky. The irritation of having all of the test cases passing, but it failing for my challenge input! I hope it doesn't scare off newcomers, but I already know a few who have given up on part 2.

I heard the question was difficult before solving it, and then I was surprised when I didn't hit any speed bumps. The overlapping case didn't even occur to me. It turns out I stumbled upon a simple solution: use two regexes. One to match the first digit, and one to match the last. Then the overlapping is a total non-issue.

Re: Advent of Code 2023 is nigh

#183

Post by abound »

hypersoar wrote: post #182
shever73 wrote: post #92

As others have said, part 2 of today's was really difficult. I finally solved it using Python regex `overlapped=true`, but it was very tricky. The irritation of having all of the test cases passing, but it failing for my challenge input! I hope it doesn't scare off newcomers, but I already know a few who have given up on part 2.

I heard the question was difficult before solving it, and then I was surprised when I didn't hit any speed bumps. The overlapping case didn't even occur to me. It turns out I stumbled upon a simple solution: use two regexes. One to match the first digit, and one to match the last. Then the overlapping is a total non-issue.

If the whole numeric part of the string was something like "eightwo", I think that solution would fail.

Re: Advent of Code 2023 is nigh

#184

Post by urda »

Udo wrote: post #124
dataengineer56 wrote: post #4

It's a tough day 1, I hope it doesn't scare off too many people. Normally day 1 is just some variation of "add numbers in a list", but this year has a mean pt 2 and a few traps for people to fall into. I wonder how long the global leaderboard will stay up before it gets hidden due to people solving with ChatGPT?

I'd actually welcome it if the leaderboard was abolished. I never really played for placement, but something about the fact that the board was full of people who routinely solve every problem in about the same time it takes me to even READ the description was a bit demotivating. I always felt this racing aspect to be somewhat at odds with the idea that this is a challenge that you can complete in your own time, maybe…

I tend to agree with this. The leaderboard for many programmers is a source of stress and is another type of internet "comparison" like seeing someone who appears "better" than you on social media. Advent of Code, to me, is a celebration of all the hard work of the year by getting a chance to show off any new skills or abilities you might have picked up.

Advent of Code should be about the solve and the sharing of a good problem together, not how fast can you cook a plate of spaghetti.

Re: Advent of Code 2023 is nigh

#185

Post by mminer237 »

AdamH12113 wrote: post #125
jjice wrote: post #101

Earlier quoted context omitted.

Same here. I would've really like if the spec specifically mentioned the possibility of that one edge case ahead of time instead of having to sift through the 1000 lines of input. No hate on AOC though, I really respect all the hard work that goes into it.

Unless the question has been edited recently, it did. There are multiple lines in the second example input that show the overlap: > eightwothree > 4nineeightseven2 > zoneight234 I test my AoC solutions incrementally by printing output, so I found that I was failing to produce the correct list of numbers in a line right away. I suppose if you're taking a faster approach and just trying to extract the first and last nu…

None of those it matters that much though. The test case of `eightwo` would be the most critical and unintutive.

Re: Advent of Code 2023 is nigh

#187

Post by wdroz »

kristaps wrote: post #8

Last year there were people solving the puzzles with LLMs, but I don't think I saw anyone get past day 5 or so. I'm interested in how well it goes this year. Please reply if you are trying yourself or can link to public attempts by others

The quickest time of the first star is suspicious...

Re: Advent of Code 2023 is nigh

#188

Post by abound »

Chobilet wrote: post #119

Without going into spoilers, its interesting that people jumped to regex to solve this. For me that was a fairly non intuitive when I first saw the problem(both parts). What jumped to me is the problem statement indicated a finite number of states and I crafted a solution based on that information. But its really cool to see how we all jump to different implementations.

I took one look at the overlaps, decided I had things I'd theoretically like to accomplish today that didn't involve tracking overlapping subsets of strings, and hardcoded the nine possible overlaps, i.e. [1]

[1] https://git.sr.ht/~bsprague/advent-of-code/tree/main/item/20...

Re: Advent of Code 2023 is nigh

#189

Post by jacksontheel »

criddell wrote: post #178
agoose77 wrote: post #140

Earlier quoted context omitted.

It shows an overlap, but it doesn't indicate how one should parse it.

It showed "eightwothree" to be 83. Or is that not what you are talking about?

If it had shown "eightwo" as the last part of a string, then people with overlap would fail the example because they'd be finding "eight" where "two" would be correct. Having it at the beginning means it was overlooked, at least for me.

Though, I have no problem with the "spec". This a code puzzle game, so figuring that out was part of the fun, in my opinion

Re: Advent of Code 2023 is nigh

#190

Post by criddell »

sokoloff wrote: post #117
Frummy wrote: post #73

Earlier quoted context omitted.

Edge cases such as "1oneight", "3sevenine", "sevenine3" (I made these up to highlight)

I’d wager that most implementations would be fine on “sevenine3”, as they’d likely get 73 for the row, whether or not they found the 9.

How about just "sevenine"?
Post reply on HN