Andrew Gallant

Given there's a question open here, I'm going to **delay the 1.0 release another week.**

> As a usability note, I wrote an application with `BStr` in the internal APis and kept getting tripped up that I needed `as_bstr()` or `.map(ByteSlice::as_bstr)` at the end of...

@lopopolo Yeah the new Cargo feature stuff is awesome. I very much like that it gives more control over what's a public feature. @epage See https://github.com/BurntSushi/bstr/issues/5 and https://github.com/BurntSushi/bstr/pull/8 for more...

Yeah that's not a 1.0 concern. I'm unlikely to take a dependency for that. Instead, I would rather see the implementation ported to bstr or maybe even memchr. That said,...

Right. I had used `bstr 0.1` in anger and the explict `BStr`/`BString` types were just really annoying. The constant converting back-and-forth was super painful and led to a lot of...

Hmmm. What about a different idea. What if we tweak the wording of the existing conversion routines in `bstr` such that they could be implemented with the raw byte representation...

cc @JoshTriplett

I'm usually a little skeptical of linking to other crates in API docs unless they're really ubiquitous, but I think I'd be okay with this specific case given that I...

> The various split functions should have variants for passing a byte instead of just str/char. I ended up using `split_str(b"\0")` and `split_str(b"\xff")` a few times which is going to...

@thomcc Oh, I also meant to ask, I'm always looking to understand use cases better. Could you share more about what you're using bstr for, if possible? (As in, what...