What could go wrong trying to solve AoC in Rust?

MaliciousKebab@sh.itjust.works to Programmer Humor@programming.dev – 65 points –

signal-2024-02-01-19-47-41-855

17

You are viewing a single comment

i didn't mean as a version. I meant as overuse of streams

How would you have preferred to solve it? Using for loops?

Python style iterator comprehension

(wonder if someone has made that into a macro. if no one has I will)

I don't think it would be readable. Too much going on. You'd need an outer iter over lines, an inner over words, a check for number and a conversion. And there would be zero error handling.

No less readable than half the Python comprehensions I've written.

zero error handling.

Not necessarily. The macro could look for a ? at the end of the final expression (the bit that comes first in a comprehension) and return a Result.

Right, of course, I meant no error handling in the Python impl