[s4s] Tribune

ok I ran a diagnostics and realized I'm fucking gay

Your fortune: ｷﾀ━━━━━━(ﾟ∀ﾟ)━━━━━━ !!!! C programmers think they can manage their own memory but they also have to foresee every possible way an end user can break their program, if they don't do this, they inevitably forget about some edge case where the user can make the program keep allocating memory and losing track of it so it never gets freed and returned to the operating system and that's how memory leaks happen, only subhumans design their software with the ability to leak memory. >>12897704
>only subhumans design their software with the ability to leak memory.
low iq take, even the linux kernel can have memory leaks. they need a os call it uhh trog.lite it compiles and does every for me as I am INCOMPETENT

Your fortune: Better not tell you now >>12897732
a lot of ppl use the word "memory leak" to refer to unbounded memory usage caused by pathological user behavior that was never forseen by the developer, none of that memory is actually leaked or wasted or "lost" to the program that allocated it, it's working as intended even if it's poorly designed, actually I am willing to double down and call this subhuman design too >>12897763
>a lot of ppl use the word "memory leak" to refer to unbounded memory usage caused by pathological user behavior that was never forseen by the developer
This isn't a memory leak.
And besides, unbounded memory usage will just result in a failed allocation, which will only cause a crash if the failed allocation wasn't handled properly, e.g.. if a memory allocation function returned an error or a NULL value and the code tried to use the unallocated pointer.
Bear in mind that if the code deliberately crashes on a failed allocation that might just be intended behavior as fully recovering from the failure might not be feasible. >make game in linux
>cross compile for windows with mingw
>runs fine in wine
>playtesters say everything is fine
>decide to try game out a week later in Windows
>render thread consistently freezes after about 30 seconds of play
it seems like memory leakish behavior. it didn't have any issues in valgrind. oh well, i can't be bothered to fix it. nobody really wanted to play my game anyway. Memory leaks will no longer exist after AI fully replaces human programmers by the end of 2026 >>12897796
lol, lmao even.
This isn't about human incompetence, it's about system complexity. The more complex a system is the harder it is to predict after time t.
the longer t is, the less accurate the prediction.
The only way to guarantee that a program is correct is by formally validating it. >>12897796
claude ai, pls make this [one tiny change] to one single translation unit in my 100k loc project

sure i just need to tokenize all 100k lines of source code and exceed your monthly token allowance with one single prompt that will use up 100 trillion billion gallons of water >>12897744
lel nice dubs

Your fortune: Average Luck >>12897817
You can't fight the future, luddite. >>12897791
*be anon
*still hasn't discovered rust
*whom quote >>12897826
Rust can have memory leaks even without unsafe code, though it's harder. >>12897704
Your biggest nightmare
free(*ptr);
free(*ptr); >>12897854
lose the asterisk, buddy. Unless the address is located at the memory address the pointer is pointing to. >>12897822
unchecked doubles on page 10! >>12897796
two more weeks we swear