(#wg7xx5q) @movq Haha 🤣 I guess I'm aiming for "if this were real, how would I approach it" 😅

(#wg7xx5q) Day 2 used lots of Cut and Split.

(#wg7xx5q) @prologic That is a lot of code, yes. 😅 Mine is shorter, has more naive searching (it searches a word like `red` and then backtracks to the number before it; completely ignoring the semi-colons because they don’t matter), and – like any good C program – will crash horribly on malformed input. 👌😂🥴 It really depends on what you’re after. I’d never write code like this in “real-world applications”. But for these puzzles and my DOS use case, it’s “good enough”. 😅

(#wg7xx5q) Day 2 used lots of Cut and Split.

(#wg7xx5q) Welcome @movq and @taigrr 👋 I dunno how you guys are doing these so far, but it took me ~2hrs to get Day 2 done 🤣 Maybe I wrote too much code 😅

(#wg7xx5q) Admittedly I _could_ have use regex to parse those lines into the structures I needed, but oh well 😅 Sometimes i hate regex 🤣

(#wg7xx5q) @xuu Yeah or in my case a lot of `strings.TrimSpace()` and `strings.Split()` because I hand-built a custom parser 🤣