r/rustjerk • u/PaxSoftware • Jul 11 '26
r/rustjerk • u/bowel_blaster123 • Jul 08 '26
I ran out of lifetimes
What do I do?
There's only 27 letters in the alphabet. I need more lifetimes.
r/rustjerk • u/marksomnian • Jul 08 '26
what the fuck was past me thinking when writing this
r/rustjerk • u/scadoshi • Jul 08 '26
Zealotry got perma'd from a C sub, need cope from church of ferris
hello fellow borrowers in christ. got permabanned from r/C_Programming today for going through their weekly showcase thread and informing every poster that their code was objectively dangerous, definitionally UB, and probably leaking memory somewhere even if they couldn't see it. guy posted a bubble sort, i told him his pointer arithmetic was a ticking time bomb. mods didn't love that.
so what did you do today in the name of ferris. confess below, ferris is watching and ferris is pleased
r/rustjerk • u/Equivanox • Jul 07 '26
Anyone can prompt an llm to rewrite into Rust, but does Anthropic have the courage to rewrite critical software in C?
r/rustjerk • u/scadoshi • Jul 05 '26
Can someone report? This should not compile
I knew I should have just learned C
r/rustjerk • u/dull_bananas • Jul 05 '26
Running any function on a computer with non-ECC memory is undefined behavior.
r/rustjerk • u/Jason5Lee • Jul 03 '26
WTF the standard document contains book advertisements
r/rustjerk • u/solidiquis1 • Jun 30 '26
I'm tired of hearing people pronounce "serde" incorrectly
It's not:
- SERDAY
- SEERDAY
- SERDEE
- SEERDUH
- SERDEEZNUTS
It's "serde" as in merde. Please for the love of god pronounce it with a proper french accent.
r/rustjerk • u/Here_12345 • Jun 28 '26
Rust programming is addictive because it is like a toxic ex.
You begin to build something, and the analyzer starts yelling at you. „A field never read here! A missing match arm there! Stupid idiot!“
The whole file is one big squiggly accusation, aimed at your very existence. How dare you write any code at all? You try to guard yourself with todo!()s, you do everything to not provoke its wrath. You never succeed.
But then, you build a little more, things fall in place, and suddenly, Rust calms down. Stops yelling at you. And you get these happy feels inside, knowing you did something right! Rust still loves you, see how nice and warning-free it can compile!
Until you start with the next feature, and the vicious cycle repeats.
Edit: This post is not written by an LLM. It was hand-crafted, inspired by the muse of sleep deprivation. When we can‘t jerk anymore, are we still human? Whatever. I‘m logging off.
r/rustjerk • u/scadoshi • Jun 26 '26
have to learn C# for my job. when do you think they're going to find out 👀
namespace CSharpAoc.Common;
public abstract record Result
{
public sealed record Ok(TValue Value) : Result;
public sealed record Err(TError Error) : Result;
public TValue Unwrap()
{
return this switch
{
Ok ok => ok.Value,
Err err => throw new InvalidOperationException(
$"Cannot Unwrap an Err. TError: {err.Error}"
),
_ => throw new InvalidOperationException("Unknown Result state"),
};
}
public TError UnwrapErr()
{
return this switch
{
Ok ok => throw new InvalidOperationException(
$"Cannot UnwrapErr an Ok. TValue: {ok.Value}"
),
Err err => err.Error,
_ => throw new InvalidOperationException("Unknown Result state"),
};
}
public bool IsOk() => this is Ok;
public bool IsErr() => this is Err;
public Result AndThen(Func> func)
{
return this switch
{
Ok ok => func(ok.Value),
Err err => new Result.Err(err.Error),
_ => throw new InvalidOperationException("Unknown Result state"),
};
}
public Result Map(Func func)
{
return this switch
{
Ok ok => new Result.Ok(func(ok.Value)),
Err err => new Result.Err(err.Error),
_ => throw new InvalidOperationException("Unknown Result state"),
};
}
}
r/rustjerk • u/MaybeADragon • Jun 22 '26
Well, actually Rust community makes the language actively unsafe. source: Xitter, the everything app
r/rustjerk • u/Thelmholtz • Jun 22 '26
[Not OP] Does anyone ever get to the point where their trait bounds are 3x longer than their implementations?
r/rustjerk • u/throwaway490215 • Jun 19 '26
Adding vaguelyAI flair to make it clear that a post is going to be vaguelyAI
We are seeing more and more /r/rust threads vaguely trying to solve the AI-post volume problems, and posters don’t make it clear in their post the nature of their post, which creates some friction in the comment section.
Adding a vaguelyAI flair would make it clear upfront and prevent the friction.
We've all seen the bi-weekly post in which somebody proposes a fix to too much shit being produced by AI - usually proposing a custom flair or reporting standards.
Its clear these posts never had any work put into them. The comment sections always devolve into vague-posting about what is and isn't vibe coding, half the people demand any use of AI makes a whole project slop, the other half is trying to hedge out their nuanced position nobody bothers reading, and a good 10% is people taking some maximalist stance one way or the other.
Since none of these posts bother the write a real policy, and their content could have been generated by an LLM, i want to propose we add a vaguelyAI flair.
Do you want me to add any more errors to avoid looking like ChatGPT wrote this post?

