Add BString convenience constructors (from Vec) about bstr HOT 3 CLOSED

Yeah I definitely want to keep them around. I purposely kept the API tiny to be conservative, in order to wait for use cases to add more as needed.

The default impl makes sense. However, I was hoping to avoid the constructors in favor of just relying on, e.g., BString::from(Vec::with_capacity(...)). Thoughts?

from bstr.

That's fine by me, had Default been present I probably wouldn't have bothered to file an issue, BString::default() is a little longer than e.g. BString::new() would be, but not exactly hard to type or remember.

from bstr.

All set. I added Default impls for BString, &BStr and &mut BStr and released the changes to crates.io in 0.2.2.

I'm definitely not strongly opposed to adding more constructor APIs to these types, but I'd like to keep them fairly spartan for now until we get more feedback.

from bstr.