This is what happens when a Python dev tries to write Rust without actually learning Rust! The code is a horrifying Frankenstein's monster of Python syntax smuggled into Rust—like that .expect("Failed to read line")
that would immediately error out since it's attached to a read operation that already completed. And don't get me started on using match
with a dot operator right after! The error handling with Ok(num) => num
looks legit until you see that bizarre Err(_) => continue
syntax that would make the Rust compiler have an existential crisis. It's basically Python wearing a Rust trenchcoat trying to sneak into the memory-safe club.
What's Stopping You From Writing Your Rust Like This?
3 months ago
124,287 views
0 shares

rust-memes, python-memes, syntax-memes, language-confusion-memes, compiler-errors-memes | ProgrammerHumor.io
More Like This
When You Don't Like C And Rust
3 months ago
142.4K views
0 shares

C Is Uncontrollable
1 month ago
121.2K views
0 shares

TS Should Have Been Rewritten In Rust
3 months ago
140.6K views
0 shares

You Need To Try More
4 months ago
184.7K views
0 shares

What Rust Looks Like To A C Dev
2 months ago
196.8K views
0 shares

The Wizard's Knowledge Buffer Overflow
2 months ago
151.5K views
0 shares

Loading more content...