MaliciousKebab to Programmer Humor@programming.devEnglish · edit-211 months agoWhat could go wrong trying to solve AoC in Rust?imagemessage-square17fedilinkarrow-up172arrow-down17
arrow-up165arrow-down1imageWhat could go wrong trying to solve AoC in Rust?MaliciousKebab to Programmer Humor@programming.devEnglish · edit-211 months agomessage-square17fedilink
minus-squarecrispy_kilt@feddit.delinkfedilinkarrow-up4·11 months agoJava 2 didn’t have streams nor iterator combinatorics, not sure what you mean?
minus-squareChinstrap@lemmy.mllinkfedilinkEnglisharrow-up5arrow-down1·11 months agoi didn’t mean as a version. I meant as overuse of streams
minus-squarecrispy_kilt@feddit.delinkfedilinkarrow-up3·11 months agoHow would you have preferred to solve it? Using for loops?
minus-squareAVincentInSpace@pawb.sociallinkfedilinkEnglisharrow-up1·edit-211 months agoPython style iterator comprehension (wonder if someone has made that into a macro. if no one has I will)
minus-squarecrispy_kilt@feddit.delinkfedilinkarrow-up1·11 months agoI 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.
minus-squareAVincentInSpace@pawb.sociallinkfedilinkEnglisharrow-up2·11 months agoNo 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.
minus-squarecrispy_kilt@feddit.delinkfedilinkarrow-up2·11 months agoRight, of course, I meant no error handling in the Python impl
Java 2 didn’t have streams nor iterator combinatorics, not sure what you mean?
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.
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