Thankfully no one writes that today because String::from is objectively superior
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
I'm in the "I was around before 1.0 where we changed the name of String twice and fucked with to_owned a million times and had to refactor from to_owned to to_string back to to_owned and now I hate ownerifying strings in any way period strings can go die in a fire" camp
I'm mostly just mad that it's `&str` and not `&String`. I don't care about the capacity, let the compiler deal with getting rid of that
-
-
Yeah but &String is more like &(&str, capacity) so even if you don't care about the capacity you still have double indirection.
-
We really could go all in on the autoderef train and start silently applying it to stuff like that at the type level. Not that I think it's a good idea, but it is interesting to think about.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.