Export BytesMut::from_vec(vec)

[al8n]

Hi, can we expose BytesMut::from_vec? Which can help avoid copying when building a BytesMut from Vec<u8>

[Darksonn]

That seems reasonable to me. We can add it as a From impl.

[braddunbar]

The comments on from_vec call out the fact that the allocation strategy may change at some point, making this a more expensive operation because it would then involve a copy. I'm not sure how likely that is and I don't have any opinions about exposing it, but I wanted to call it out here since this would be a departure from that stance.

bytes/src/bytes_mut.rs

Lines 824 to 829 in 327615e

	// For now, use a `Vec` to manage the memory for us, but we may want to
	// change that in the future to some alternate allocator strategy.
	//
	// Thus, we don't expose an easy way to construct from a `Vec` since an
	// internal change could make a simple pattern (`BytesMut::from(vec)`)
	// suddenly a lot more expensive.

[Darksonn]

Yes, good point, thanks.