Hacker News new | past | comments | ask | show | jobs | submit login

From my personal experience I think Rust's string system is hard to beat at the moment. It's pretty darn good from a usability point of view and it also found a nice solution to work with UCS2 windows APIs by providing a OsStr type.



I’m glad that Rust strings aren’t indexable by integer, but I think that making them indexable by range (of UTF-8 code unit offsets) was an error. `foo[0..10]` should have been `foo.slice(0..10)` or similar instead.


It’s a bit of a footgun indeed but it’s quite handy in combination with the char index iterator.


Sure, you do want to be able to index by code unit range, but it shouldn’t have been with the Index trait.


There's no reason this couldn't be added now, though, right?


The only annoyance is the occasional unwrap, when something is provably impossible, but the type system can't detect it.


That’s what `unwrap` is for, though.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: