chromeleonMe, after carefully reading Rust's ownership and borrow checker rules
The rule of thumb I always tell people is that they should generally put owned data into struct fields and references into function parameters.
I recently learned you can pass a
&String to a &str parameter, so that’s neat.
Ah yeah, via deref coercion, which is also called “auto-dereferencing” at times. Not to be confused with “auto-referencing”, which is also a thing^1.
You can do some wild shit with deref coercion. And when I say “wild”, I guess, I’m talking about the most normal thing for Java devs, because well, it’s a lot like inheritance. 😅
Basically, this concept of being able to pass &String into a parameter that takes &str also applies to the self parameter. Or in other words, methods implemented on str can also be called on String, as if String extends str.
And well, obviously you can also make use of that yourself, by writing your own wrapper type. You can even “override” existing methods in a sense by re-defining them in the wrapper type.
I had to play around a bit with it myself, so here’s a playground: play.rust-lang.org/?version=stable&mode=debug&edi…
Welp, I posted my hot take that impl Deref is similar to inheritance as a meme in [email protected]: lemmy.ml/post/42514248
Now, let’s see how many feathers get ruffled. 🙃
