efim
/
Advent-of-Code-2023
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Advent-of-Code-2023/day10/notes.org

694 B
Raw Blame History

Notes

part 2.

how would i even try to check of 'in' or 'out' of the loop? i guess i could mark things while i go through the loop?

or, i could count manually?

i could change neighbors of the beast point. then do one more pass around, setting bool 'onMainPath' to true and then change all else to .

i guess i could then do one more pass, and mark as 'I' and 'O' closest line of .

another idea i don't really want to pursue - 'color fill from some corner' this is also painful due to pipes touching still need to let the 'O' filling in.

but yeah, if i make initial filling in of the I, then i could just fill in all . with I until nothing changes. and count I

sounds like a plan