Notices by karna :flipflop: :buffsuki: (karna@poa.st), page 4

@Inginsub I dont really follow the vim changelog so I have no idea why a seemingly simple set of macros would break like that.. its a strange situation for sure

@Inginsub :f:

@Inginsub maybe your distro changed some global settings in an update or something :akarinShrug:

@Inginsub Well. Thats a "clean" vim setup for you... I'm guessing there may be some config/extension somewhere ccausing the makefile issue but it may not be worth chasing that rabbit hole since you have a fix

@Inginsub --clean is the option I think

@Inginsub thats really strange... Ive never had to do that ever either. I wonder if it still happens if you run (n)vim in the mode where it doesnt load any user settings/extensions..

@Inginsub stray modeline or editorconfig file?

@mikuphile I always wondered why some japanese instances' timelines always looked like a series of subpoasts... what you said explains it pretty well

@Inginsub @hazlin eggcelent :nigga_smiles_in_polish:

@Inginsub @hazlin Part of me says thats smart, but another says this nigga is cheating

@Inginsub @hazlin Do you have code for input parsing too? I assume you aren't doing that by hand..

cc @hazlin here's the prompt, test, and input files like before

@Inginsub @hazlin I agree, we dont talk about smalltalk java

@Inginsub @hazlin oh i didnt do the APL stuff this year, it was 2022 I think, so no spoilers there (unless you are saving 2022 exercises for another day too). This year I tried rust as my unfamiliar language of choice (I typically pick an unfamiliar language and do aoc for a specific year with that). Doing 25 entirely different languages sounds like it would be either very fun or very annoying by the end of it.

@Inginsub @hazlin If you want to see true line noise, I had done one aoc in APL and at some point implemented either bfs or dfs in it... it was something to behold

@hazlin Sure, the text is too large for a single poast, so I'm poasting three files: the prompt, the test input (same as your screenshot), and the actual input (which I believe is randomized for different users). the answers to test.txt and input.txt are in the prompt file itself.

Not using regex made this feel so much more inelegant

tried to make main shorter since the rest was longer.. I couldn't figure out a clean way to do this with only iterators and no explicit loops (but loops are just syntactic sugar for iterators here so it kind of works)