Are any other @rustlang folks bothered by `Vec` over `Vector` but `Option` over `Opt`? (And a billion other things that are abbreviated that don't need to be)
-
Isn't &String currently a thin pointer, while &str is fat?
Yes. I fully understand the differences between the types, and the technical reasons they are separate. As a user I don't care, this is a compiler/language problem
-
-
Don't get me wrong, I'm asking as a bounds check before I say something stupid, not to be a language lawyer
-
Sorry for assuming. -- Yes, you are correct. `str` is basically `[u8]` which is guaranteed to be valid UTF-8. As an unsized type, it cannot appear on its own. &str is a fat pointer which also contains the length. 1/2
- 1 more reply
New conversation -
-
-
Explaining "this type can never appear on its own" to a Rust newbie is a major hurdle
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.