262
Me, after carefully reading Rust's ownership and borrow checker rules (lemmy.world)
submitted 9 months ago by to c/programmer_humor@programming.dev
17 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 44 points 9 months ago (5 children)

The rule of thumb I always tell people is that they should generally put owned data into struct fields and references into function parameters.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 11 points 9 months ago (2 children)

    I recently learned you can pass a &String to a &str parameter, so that's neat. 

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 9 points 9 months ago (1 child)

    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: https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=af65ed396dec88c8406163acaa1f8f8d

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 9 months ago

    I like this rule of thumb and it goes nicely with the “if you have more than 3 arguments to a function, consider making a struct to pass the arguments in” rule of thumb because

    You can have the struct use a named lifetime (or several) for the different parameters so it doesn’t own them!

    Best of both worlds.

  • permalink
  • fedilink
  • source
  • parent