←back to thread

Flattening Rust’s learning curve

(corrode.dev)
451 points birdculture | 1 comments | 13 May 25 22:25 UTC | HN request time: 0.259s | source
Show context
baalimago ◴[14 May 25 05:32 UTC] No.43981145[source]▶
>For instance, why do you have to call to_string() on a thing that’s already a string?

It's so hard for me to take Rust seriously when I have to find out answers to unintuitive question like this

replies(7): >>43981274 #>>43981417 #>>43981621 #>>43981663 #>>43981709 #>>43981713 #>>43982610 #
akewovtsn ◴[14 May 25 07:09 UTC] No.43981713[source]▶
Python community famously learned the hard way that sometimes the programmer needs to know that there are multiple kinds of string.

Personally, I’ve been using to_owned instead. Some of the people looking at my code don’t write rust, and I figure it makes things a bit easier to understand.

replies(1): >>44003304 #
1. int_19h ◴[16 May 25 09:15 UTC] No.44003304[source]▶
Modern Python has a single type of string.

What used to be called "string" in Python 2 is no longer called that, precisely so as to avoid unnecessary confusion. It's called "bytes", which is why the question of "why do I have to convert it to string?" doesn't arise.