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?
1 month ago
101,915 views
0 shares

rust-memes, python-memes, syntax-memes, language-confusion-memes, compiler-errors-memes | ProgrammerHumor.io
More Like This
Side Project
2 months ago
132.3K views
0 shares

Oh Yes, Rust Gonna Fix That
1 month ago
92.7K views
0 shares

C++ With Seatbelts
26 days ago
92.1K views
0 shares

Dudes Who Learn Programming Will Turn Into One Of Four People
8 days ago
83.6K views
0 shares

I Hate Memory Safe Low Level Languages
23 days ago
90.5K views
0 shares

Blazingly Fast For First N Minus 3 Packages
21 days ago
86.9K views
0 shares

Loading more content...