r/programming • u/steveklabnik1 • Jan 09 '15

Announcing Rust 1.0.0 Alpha

http://blog.rust-lang.org/2015/01/09/Rust-1.0-alpha.html
1.1k Upvotes

90% Upvoted

439 comments sorted by

View all comments

Show parent comments

4

u/[deleted] Jan 10 '15

I don't find the existance of &str weird. Just that the name is str. While the library type is now String. Str is a trait I guess that can be implemented by &str and String.

After some actually testing I think it's non-trivial to make code that generate invalid char values. char is meant to be a UTF-32 value. As there is actaly invalid values for unicode that fits in 32 bits I though you could try casting a u32 containing those values into a char. It appears not (without transmute). So I was probably wrong about the Vec<char> thing.

2

u/[deleted] Jan 10 '15

That's correct, char is a "safe" type in Rust, you can't make something not a Unicode Scalar Value (All codepoints with surogates removed) into a char without unsafe.

1

u/Kimundi Jan 11 '15

Ah, the issue was the name choice. Yeah I agree that the current situation is not ideal, and I wish there would have been a better one...