I peeked at the puzzle input and got very intimidated.
Then I read what I have to do for Part 1 and was put temporarily at ease:
I can use a simple regular expression to do that!
I had to remember to escape the parentheses, then I got this working regex:
/mul\((\d*),(\d*)\)/g
Now I need to do the appropriate extraction and math for each match
Here is the full working code:
let total = [...input.matchAll(/mul\((\d*),(\d*)\)/g)].reduce( (total, match) => { total += match .slice(1, 3) .map(Number) .reduce((a, b) => a * b); return total; }, 0 );
It generates the correct answer for the example input.
Trying on my puzzle input generates...
The correct answer!!!
Deep breath...........
............for Part 2
I figured that since the input is full of different words, it was going to add all sorts of new rules to account for.
Thankfully, just two new words that act as starts and ends for valid mul statements.
This now feels like an exercise in isolating each stretch of valid statements by indexing each do() and don't() and searching the right portions for mul statements to parse.
I want to use regex to match all occurrences of do() and don't():
/don't\(\)|do\(\)/g
With that, I should have alternating checkpoints along the path of the input string.
If so, I can extract substrings between a do() and don't() checkpoint, and check for muls.
Let me confirm on both example and full inputs.
Here's my algorithm for isolating the flag and its index:
let flags = [...input.matchAll(/don't\(\)|do\(\)/g)].map((el) => { return [el[0], el.index]; });
Confirmed:
This just got a bit more complicated.
Since things start enabled, I must grab from index 0 until the first don't(). So, I need to find its index. And check that substring.
From then on, I can skip all subsequent don't()s, and look for the next do().
With that as my new starting index, I need to find the next don't(). That's my new end spot. Check that substring.
And repeat: find next do(), find next don't(), check substring.
This feels like a while loop.
I'll know more when as I write my algorithm.
Lots of conditions to handle the pattern-lacking do-don't occurrence order:
/mul\((\d*),(\d*)\)/g
To my gleeful surprise, it generates the correct answer for the example input.
What will it generate after processing my puzzle input?
...
The correct answer!!!
Before I checked, though, I added a console logging statement to confirm each start and end index for the substring to check.
I compared them to the order of flags in the array.
Everything looked right, so I submitted.
And got the correct answer!
What a delightful and rewarding feeling!
Another early day. Another hard-earned two gold stars.
On to Day 4!
The above is the detailed content of Mull It Over. For more information, please follow other related articles on the PHP Chinese website!