388
borrow checker? (lemmy.world)
submitted 1 month ago by to c/programmer_humor@programming.dev
108 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 month ago (1 child)

I do not get it. Aside from the fact that the supposed "creator" writes a bit like he processes every sentence through AI-translation software... which might as well be reddit feature.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 27 points 1 month ago (1 child)

    The borrow checker is a feature of Rust's compiler which places strict constraints on ownership of data to guarantee memory safety. It adds a lot of friction to writing Rust code if you're not experienced with the language (or sometimes even if you are). OP refers to the "language restriction of Rust", seemingly talking about the borrow checker, but has never even heard of it. It's kind of like someone claiming they didn't vibecoded their C++ project but having no idea what the STL is.

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

    Sounds like java garbage collector but backwards... perhaps I will understand it better if I ever try Rust.

    Thank you for explanation, YaBoyMax

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 12 points 1 month ago

    Yes, the end goal is very similar to a garbage collector. Both are advanced systems of memory management.

    The most important difference being that a garbage collector runs at runtime, while the borrow checker at compile time. Which means that the borrow checker has 0 impact on the program's performance. It just takes longer to compile the program.

    Which also means that, while the garbage collector says "you can do whatever you want with memory, don't worry about it, I'll handle it for you". The borrow checker says "you fucking donkey. Why did you do that? I won't compile this if you don't fix it".

    So you trade programmer comfort for performance (end user comfort).

  • permalink
  • fedilink
  • source
  • parent