Rust is still in the locker room having an argument with their coach (borrow checker).
Programmer Humor
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
C++ is home sick, currently the doctor (compiler) is not sure whether it's got the flu or a terminal cancer.
terminal cancer
"I'm sorry, you've been diagnosed with :(){:|:&};:"
"You have a couple seconds to live."
Why is the crab not Rust. This is outrageous, it’s unfair
Rust would be some borrow checker compile error like
borrowed data escapes outside of associated function
argument requires that `'1` must outlive `'static`
rust errors are funny if you don't know rust
News at Ten: Borrowed Data Escapes Outside of Associated Function
Those also happen to be errors you'd typically run into, if you don't yet really know Rust...
I do run into them even though I use Rust for ~3 years now, but only in non-obvious cases, e. g. when all references to the borrowed data are dropped before the end of the function.
Not a word of a lie, I saw a "segmentation fault" error in JavaScript.
Can't remember how we resolved it, but it did blow my mind.
Technically any language runtime can end in a segmentation fault.
For some languages, in principle this shouldn't be possible, but the runtimes can have bugs and/or you are calling libraries that do some native code at some point.
Ive also seen this, but not from js but node
I have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
Yup, can confirm. We had a wrapper to a C++ library using JNI, so whenever this library crashed so did the entire JVM.
The puffer fish is Bash
Yep, it's the one starting everything.
And doing nothing else. And still something manages to no be right.
I find it funny that the pufferfish blows up at its own gunshot
Why is openbsd the referee?
Rust isn't shown because it's already completed the course
No NullPointerExceptions in Kotlin.
The humble !!
operator.
Well, also the fact that all variables are non-nullable by default anyway.