3 ms·
The borrow checker is definitely a pain, but it stops being such a pain once you design your types around ownership and passing around non-owned pointers or ref
by PittleyDunkin 2y ago
The borrow checker is definitely a pain, but it stops being such a pain once you design your types around ownership and passing around non-owned pointers or references or indexes.
- lsllc 2y agoThis. I've found the same, being effective in Rust really requires that you change your way of thinking about your data structures (and code layout). Once I realized that, I was no longer fighting the borrow checker and I've been about to build complex code that more or less worked immediately. As I look back on it, I think what a pain it would have been to write and debug in C, although doing it in C would appear to be "easier".