frens, is there a different way to express `(&mut iterator).take(161)`?
(For those who are curious, the above gives me an iterator over the next 161 items without that consuming the iterator. That means that after that scope, I can still work with the iterator.)
I think it's fine, but perhaps there is a method I don't know about that expresses the matter in a more.. explicit way?
@ma3ke clippy suggests .as_mut() for the .take() combinator for Read impls
@ma3ke the zip crate casts to an &mut dyn Read to do this in one spot
@hipsterelectron
good one, may end up doing that little .as_mut() in the end.
@erk yes, I love next_chunk a lot! for other use cases it would fit the bill even better than take, but in my current case I only know how many lines are coming my way at runtime.
moreover, I'm targeting stable for the thingy I'm currently working on.