Andrew Gallant

Note that I've published `1.0.0-pre.1` to crates.io. It's not on docs.rs yet though.

[dddd0 on reddit asked](https://old.reddit.com/r/rust/comments/vsd281/bstr_10_request_for_comments/if20prs/): > Might as well ask here: Why does for_byte_record_with_terminator in BufReadExt consume self / the underlying BufRead? It doesn't seem to be necessary to me. Indeed,...

@omac777 Let's please try to keep this thread focused on 1.0 concerns. This isn't an RFC for any arbitrary feature requests, but issues specific to a 1.0 release. I've moved...

OK, the docs for what's currently on master have been published: https://docs.rs/bstr/1.0.0-pre.1/bstr/ (I haven't made the changes to stop consuming `self` for some of the methods on `BufReadExt` yet.)

@Byron I think these are the related issues for that, right? #84 and #86. I specifically skipped over those because I do not _believe_ there are any breaking changes required...

> I found myself creating little helper methods for that throughout the codebase. Can you create a new issue with these? That is, just copy and paste your helper routines....

I've added another breaking change: **restructure serde feature flags** Now that bstr has an 'alloc' feature, we need to rethink how we setup the serde feature flags. Previously, all we...

I've added another breaking change: several methods on `BufReadExt` now take `&mut self` instead of `self`.

@epage Yeah I mused about this here: https://github.com/BurntSushi/bstr/pull/111#issuecomment-1180477086 Basically, I kind of feel like 1.60 is really way too new. My first approximation is to track Debian stable (which is...

With respect to MSRV, if Rust 1.60 is too new for some folks, then I suppose they could stick with `bstr 0.2` until Rust 1.60 is no longer too new.