From the article:
> multiplied does not: it starts off 0, and every time it is multiplied via multiplied = multiplied * count it remains 0.
The article then goes on to use that fact for some optimizations.
> multiplied does not: it starts off 0, and every time it is multiplied via multiplied = multiplied * count it remains 0.
The article then goes on to use that fact for some optimizations.
It starts at 0 and keeps multiplying itself with integers, which should always result in 0.
EDIT: My bad, it is explained after the code snippet, but not immediately after so I didn't catch it at first.