Why Rust closures are somewhat hard

Re:Why Rust closures are somewhat hard by drbawb on Tuesday September 11, 2018 @12:42PM (#17961301)

Agh! Chunks is what I was looking for! I was trying to whip up an example[1] and was positive I had used a pair-wise iterator before. The best I came up w/ was zipping two iterators of the hi/lo bytes. -- I feel the parent's pain, because this is coming from someone who has been programming Rust since it had green threads and `~ / @` pointers.

I love Rustdoc, but I really wish it wasn't so obtuse when it came to casually browsing the various iterator traits. Perhaps Steve, for the benefit of myself and thread parent, you could point us to some better-edited literature for the various iterator methods?

P.S: just wanted to add, if I were faced w/ this issue in production code, I likely would've just reached for the excellent byteorder[2] crate. It's so useful for "bit twiddling" like this.

[1]: https://play.rust-lang.org/?gist=4b4ff7263d9744caeb8bacd4c0d...

[2]: https://docs.rs/byteorder/1.2.6/byteorder/trait.ReadBytesExt...

[ Parent | on HN ]

Re:Why Rust closures are somewhat hard by steveklabnik on Tuesday September 11, 2018 @01:02PM (#17961449)

Ah yeah, byteorder would be the right call.

> Perhaps Steve, for the benefit of myself and thread parent, you could point us to some better-edited literature for the various iterator methods?

I used that page to find this. I knew it was "chunks" or "windows" or something, so I just looked at them (I guessed windows, but I was wrong).

[ Parent | on HN ]