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!)
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.
oh my, oh my. so this week i have a little more time to hack on the #rust #tui #daw but... it's a mess 😬
trying to genericize the Render trait over render inputs/outputs (`ratatui::Buffer` + `ratatui::Rect` -> `Result<Rect, Box<dyn Error>>`) so that i can try passing parent focus state into the render inputs, and be done with the whole "how to focus widgets" thing
it works when passing them as two separate args, but wrapping them in a struct trips up the #borrowchecker ... ouch
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.
https://blog.polybdenum.com/2023/03/05/fixing-the-next-10-000-aliasing-bugs.html
I'd be really interested in building a toy borrow checker for Typescript, curious if that'd be able to catch strange bugs
Fighting with the #BorrowChecker is a rite of passage for new #Rustaceans. 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! #Rust is a wonderful gift! :ferris:
Completed day 4 of #AdventOfCode in #rust! I think it was actually easier than day 3, but I had a big fight with the #BorrowChecker, as we all do from time to time. Something about trying to reference elements of a vector while iterating through that vector... It is amazing all the abstractions #Python and #JavaScript do for programmers.
https://github.com/ks982579/coding-challenges/tree/main/aoc20231204
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++
Getting the #Rust #ESP board to work was really simple. Maybe the #borrowchecker and I will become friends, some day?
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!
I’m just also gonna note that Rust is always undefeated in memory allocation. #borrowchecker
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
`my sanity` does not live long enough 🙄 #rust #borrowchecker
This thread on the #rustlang forum has taught me so much more than any other resource about the #borrowChecker that I think its content should become part of some official docs (like a deep dive section in the #rustBook ) https://users.rust-lang.org/t/what-is-a-good-mental-model-of-borrow-checker/86806?u=tlaferriere
I just completed "No Space Left On Device" - Day 7 - Advent of Code 2022 #AdventOfCode https://adventofcode.com/2022/day/7
Screw the #borrowChecker, #python rulez!
https://github.com/benallard/advent/blob/master/2022/day7.py
:rust: Borrow Checker
#Primeagen does a brilliant job of describing what is #borrowChecker in #rust
https://www.youtube.com/watch?v=ZNFdkTIzdXM
As in the past I had learnt C & C++ I know about value vs reference so it was easy for me to grasp the concept.
The one "#IllegalTrick" to make #rust's #BorrowChecker shut the hell up :)
"The Rust Borrow Checker - A Deep Dive", Nell Shamrell-Harrington (https://www.infoq.com/presentations/rust-borrow-checker/).
Via HN: https://news.ycombinator.com/item?id=31432005
#Rust #Video #TechTalk #Presentation #Programming #BorrowChecker #MemorySafety #PLDI #Compiler #DeepDive
“10 Key Learnings In Rust After 30,000 Lines Of Code” [2019], Dotan Nahum (https://jondot.medium.com/my-key-learnings-after-30-000-loc-in-rust-a553e6403c19).
Via HN: https://news.ycombinator.com/item?id=30554815
#Programming #Rust #Go #GoLang #Build #BorrowChecker #Crates #Cargo #CPlusPlus #C #GarbageCollection
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
