home.social

#borrowchecker — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #borrowchecker, aggregated by home.social.

  1. 🚀 Ah, the dream of turning off Rust's borrow checker—because nothing says "I'm a coding genius" like breaking one of the language's core features for a laugh. 😂 But never fear, the "youcan" crate's here to let you shoot yourself in the foot with both barrels! 💥
    docs.rs/you-can/latest/you_can #RustLang #YouCan #Crate #CodingHumor #BorrowChecker #ProgrammingJokes #HackerNews #ngated

  2. The Algebra of Loans in Rust, nadrieril.github.io/blog/2025/.

    An excellent article by Nadri about discussions happening around teaching the Rust borrow-checker to understand more things than just “shared borrow”/“mutable borrow”. Let's discover `&own T`, `&pin T`, `&pin mut T`, `&pin own T` and `&uninit`.

    #RustLang #BorrowChecker

  3. Oh, the horror! 😱 A programmer doesn't adore Rust's beloved borrow checker—the very feature that keeps us from diving headfirst into memory chaos! 🚀 Apparently, some folks just can't handle the thrill of safe, speedy code without the comforting presence of runtime garbage collection. 🤦‍♂️
    viralinstruction.com/posts/bor #programming #Rust #memorymanagement #borrowchecker #codequality #developerhumor #HackerNews #ngated

  4. So, this is an interesting thing from the Browser Company, dia. It did generate this article based on my blog and believe me, it does sound like me.

    Scary, right?
    #AI #ArtificialIntelligence #Coding #RustLang #ProgrammingHumor #DevLife #Productivity #TechTrends #Automation #LearningToCode #Debugging #BorrowChecker #TechReflections #selftaught
    (even the tags are ai generated!)

  5. So, this is an interesting thing from the Browser Company, dia. It did generate this article based on my blog and believe me, it does sound like me.

    Scary, right?
    #AI #ArtificialIntelligence #Coding #RustLang #ProgrammingHumor #DevLife #Productivity #TechTrends #Automation #LearningToCode #Debugging #BorrowChecker #TechReflections #selftaught
    (even the tags are ai generated!)

  6. So, this is an interesting thing from the Browser Company, dia. It did generate this article based on my blog and believe me, it does sound like me.

    Scary, right?
    #AI #ArtificialIntelligence #Coding #RustLang #ProgrammingHumor #DevLife #Productivity #TechTrends #Automation #LearningToCode #Debugging #BorrowChecker #TechReflections #selftaught
    (even the tags are ai generated!)

  7. So, this is an interesting thing from the Browser Company, dia. It did generate this article based on my blog and believe me, it does sound like me.

    Scary, right?
    #AI #ArtificialIntelligence #Coding #RustLang #ProgrammingHumor #DevLife #Productivity #TechTrends #Automation #LearningToCode #Debugging #BorrowChecker #TechReflections #selftaught
    (even the tags are ai generated!)

  8. So, this is an interesting thing from the Browser Company, dia. It did generate this article based on my blog and believe me, it does sound like me.

    Scary, right?
    #AI #ArtificialIntelligence #Coding #RustLang #ProgrammingHumor #DevLife #Productivity #TechTrends #Automation #LearningToCode #Debugging #BorrowChecker #TechReflections #selftaught
    (even the tags are ai generated!)

  9. I did, during my previously mentioned workshop, do one thing to offend #Rust’s #borrowchecker. I was implementing an Account struct that had a current balance and a Vec containing a history of balances. This was using #PyO3 so there are some special types. Because of inheritance, I have self_ instead of self. Here’s the bad thing I said:

    self_.history.push(self_.as_super().balance);

    @algo_luca had to explain it to me. He didn’t even need to think about it. He instantly knew what was wrong. Now I am enlightened. I won’t make this particular kind of mistake again.

    Of course the mistake is that I was trying to use a mutable reference (so I could push to history) and anything else at the same time.

  10. I spent the last 2 hours dealing with C++ value categories in templated code.
    Could someone please kill me?

    Most people focus on the #BorrowChecker when they compare #RustLang and #CPP, but I feel that it should also be highlighted how much more intuitive (and a lot saner) it is to deal with moving/copying/referencing in Rust.

  11. Fighting with the is a rite of passage for new . But once you get to know the hardware and the borrow checker, you start to see why it complains all the time. It makes you wonder - "Could I have prevented these mistakes on my own?". Clearly not - you manage to trigger it all the time, after all! is a wonderful gift! :ferris:

  12. I figured my issue with rust: it's alloc anxiety. Every time I have to do explicit allocations I feel like I’m doing things wrong, not fighting the borrow checker enough, or not writing the proper APIs.

    And that inner gripe with the poisonous taint of `clone()` makes me feel like I failed as a programmer, because I should have known my tool better.

    Reasoning with that, I start to feel there are many cases where allocating is just not a problem, and it's something you can optimize for after the rest is done. Even though, at times, it means that you need to redesign some inner workings.

    Oh, also, rust sucks to read, but nowhere close to C++

    #rust #borrowchecker #anxiety

  13. The way I write #Rust is by first thinking of the code in #Haskell and then translating it to Rust, while praying that the #BorrowChecker doesn't get in the way!

    #FunctionalProgramming #RustLang

  14. I’m just also gonna note that Rust is always undefeated in memory allocation. #borrowchecker

  15. #RustQuiz

    What's the output?

    A. It will print "hello"
    B. It will print "rusty"
    C. It will give a compilation error
    D. It will give a runtime error

    #rustlang #rust #borrowchecker

  16. `my sanity` does not live long enough 🙄

  17. Feel like I achieved something today. Got a nice #treeStructure going in #Rust, with a lot of convenient functionality, that finally satisfies the #borrowChecker! Doing something in Rust is almost always rewarding when you're new to it, because you've likely spent many hours battling through compile errors and re-architecting your solution. #myJourneyWithRust

  18. Feel like I achieved something today. Got a nice #treeStructure going in #Rust, with a lot of convenient functionality, that finally satisfies the #borrowChecker! Doing something in Rust is almost always rewarding when you're new to it, because you've likely spent many hours battling through compile errors and re-architecting your solution. #myJourneyWithRust

  19. One of the most problematic choices in the #rust #programmingLanguage is to have a separate String, &str, and str. How novice adapts don't lose their minds over the #borrowchecker is beyond me.

    This problem does not exist for primitive characters, numbers, and booleans. Only for "strings".

  20. Rust pattern: Iterating an over a `Rc<Vec<T>>`, smallcultfollowing.com/babyste.

    A very instructive discussion about how to iterate a `Rc<Vec<T>>` while getting the borrow checker happy. Must read.