Axel Wagner <axel.wagner...@googlemail.com>:
> The key term was "occasionally". I don't know how often "iterators that
> don't need any error handling or cleanup" comes up, but I'd imagine it to
> be pretty rare. In Python, for example, this might be a bit different,
> because the iterator can just throw. And if you actually don't need error
> handling or cleanup, using a channel seems fine (and on par with any
> generic iteration construct in terms of LOC).
>
> If saving LOC is the goal (TBH I contest that all LOC are created equal in
> this regard) there are much lower hanging fruit.
My "low-hanging fruit" is the real problems I'm encountering
tranlating 14KLOC of algorithmically dense Python that operates on
data sets gigabytes wide (translation now 70% complete). I think
that's a pretty good road test.
You shouldn't assume I don't have ideas about error handling and cleanup
just bceause you haven't seen them yet. They's be in a complete RFE.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
