• The whole point of it is to prevent you from doing stupid shit. Yes it’s annoying. But you can’t handle memory management on your own, no matter how much you think you can.

    It’s either that or garbage collection. Choose which one you hate less.

      • That’s what the unsafe keyword is for. HOW DARE THE BORROW CHECKER QUESTION MY DECISION TO RETURN A REFERENCE TO A TEMPORARY!

    • Garbage collection doesn’t solve the problem either, cause it’s too unpredictable and typically doesn’t even give you the option to close resources when memory is reclaimed. So just opening SQL connections and forgetting to close them will quickly drain the connection pool.

    • I mean, I really like the zig approach. It usually turns into “the caller is responsible for managing the memory”

      But then when I’m the caller I sweat a little.

      • when I’m the caller I sweat a little

        I too much prefer to send a text or email.

  • I don’t understand why people hate the borrow checker. Just make sure that you own the value until everything is done using it, or put it into a smart pointer

    • I basically never have borrow checker issues at all anymore, and smart pointers are basically never necessary. It takes getting used to, but it stops being an obstacle with practice.

      • Yup. Although I like smart pointers due to their simplicity (unless it really needs performance), as well when dealing with tokio’s spawn (eww. Smol and future combinators are way better)

        Although trait bounds are always a bigger issue for me… probably because of my biblically accurate trait bounds