Choosing a more optimal `String` type
swatinem.de
Choosing a more optimal `String` type
1–10 of 24 posts
Re: Choosing a more optimal `String` type
#2Re: Choosing a more optimal `String` type
#3Re: Choosing a more optimal `String` type
#4Re: Choosing a more optimal `String` type
#5Why use strings and pass them around in the first place? Why not limit the use of String types to system boundaries where data must be serialized into or from character-oriented streams?
Re: Choosing a more optimal `String` type
#6‘More optimal' is oxymoronic; ‘better’ is just that.
Re: Choosing a more optimal `String` type
#7‘More optimal' is oxymoronic; ‘better’ is just that.
Although "optimum" is an absolute term, like "unique", it became common verbal practice to make it relative: "not quite optimum" or "less optimum" or "not very optimum". Mel called the maximum time-delay locations the "most pessimum".
https://users.cs.utah.edu/~elb/folklore/mel-annotated/node1....
Re: Choosing a more optimal `String` type
#8Aaah, `Cow`, the unloved child ...
Re: Choosing a more optimal `String` type
#9‘More optimal' is oxymoronic; ‘better’ is just that.
From 1983: Although "optimum" is an absolute term, like "unique", it became common verbal practice to make it relative: "not quite optimum" or "less optimum" or "not very optimum". Mel called the maximum time-delay locations the "most pessimum". https://users.cs.utah.edu/~elb/folklore/mel-annotated/node1....
Re: Choosing a more optimal `String` type
#10See https://github.com/rosetta-rs/string-rosetta-rs for some more analysis. HipStr also has a decent table [1]
[0] https://www.reddit.com/r/rust/comments/117ksvr/ecow_compact_...