bytes VS text

Many Rust code examples I come across online represent bytes as &[u8] or Vec. However, there is a Bytes crate. Is there any reason for preferring the vector or the slice instead of this crate for bytes?

Take a look at the Bytes crate. With it, one can buffer bytes into a BufMut, and send borrowed slices as Bytes. Once the Bytes are freed, the BufMut takes care of reusing the capacity. Several of the web server frameworks use this, so it's fairly mature.

The project is led by the Tokio community — most of the implementation so far has been done by people who are Tokio project maintainers. Tokio hosts a number of libraries that aren't tightly coupled to the tokio crate's runtime, like prost and bytes. The name just means that the same group of people is committed to working on and maintaining it. :)

Oh an libraries (or the std library) that want to write unsafe code that relies on some Trait's invariant will mark that trait `unsafe`, for example: https://github.com/tokio-rs/bytes/pull/432

String is a linked list of UTF-32 codepoints, which is just as bad as it sounds. Haskell programmers usually use Text from the text package instead.

This is the first release that was executed via the new GitHub CI. Everything went smoothly, except for an unexpected packaging bug on windows due to text-2.0 linking against libstdc++ by default.

In addition to what's mentioned, the "default" libraries people use are often not the best-performing ones. E.g. Data.Vector.Hashtables is often much faster than Data.HashMap.Strict (which again is typically faster than Data.Map). And we find performance papercuts in common libraries that may simply be due to not enough people optimising for speed.

Used by nearly every Haskell project: https://hackage.haskell.org/package/text 60% of the modules are ".Internal".

text

Here is a representative patch for text: https://github.com/haskell/text/pull/365/commits/37a2157245457a287d638bbceb472fe93b71f224 Hopefully it clarifies why achieving C performance is problematic even if you have enough primitive operations.

I want to run an app in a Docker container, but detached. This causes getLine to throw an EOF exception, since the terminal detaches. That is, if I understand this thread correctly https://github.com/haskell/text/issues/258.