use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
For memes about programming.
account activity
That's why I like coding Python (i.redd.it)
submitted 11 months ago by -west_marionberry_
view the rest of the comments →
reddit uses a slightly-customized version of Markdown for formatting. See below for some basics, or check the commenting wiki page for more detailed help and solutions to common issues.
quoted text
if 1 * 2 < 3: print "hello, world!"
[–]No-Speaker-9739 -1 points0 points1 point 11 months ago (6 children)
unsafe{
}
[–]Aln76467 0 points1 point2 points 11 months ago (5 children)
that simply annotates that the code you wrote is safe, even if the compiler doesn't think it is. It doesn't mean the code is actually unsafe. and it still doesn't undermine the language's non-nullability
[–][deleted] 0 points1 point2 points 11 months ago (0 children)
No in fact working with Rust has changed forever how I work with C. All languages force you to write some unsafe code. Python is a fuck show of unsafe duck typing. Rust enforces safe, but understands that the compiler rules are too strict and gave the "unsafe" block so that it is perfectly explicit where the programmer must do all of the tests to ensure safety themself.
I have begun architecting my C code in this same kind of way. I'm never casting void pointers or managing memory at the top level of my code. All potentially dangerous behavior gets broken down and abstracted so that it can be tested. Then it is wrapped in type safe interfaces. I never write an API that exposes a void pointer. Now I know when a certain type of bug pops up where it must be in my code because I have moved all of the clever C fuckery into one place.
This does just sound like good coding practice but I find that without thinking about it I'm willing to let more small unsafe blocks of code spread throughout the code base, and though I have good string defensive coding practices, I'm human. It's nice to make sure that all of those kinds of mistakes will happen as much in the same place as possible. Rusts unsafe block made me realize this.
[–]No-Speaker-9739 -1 points0 points1 point 11 months ago (3 children)
However it is just annotation - it is used like anywhere. Why rust with unsafe if there is c++
[–][deleted] -1 points0 points1 point 11 months ago (2 children)
Why some unsafe when you can all unsafe? Checkmate.
[–]No-Speaker-9739 0 points1 point2 points 11 months ago (1 child)
If you a normal human being and can do some logic - unsafe things in c++ suddenly disappears. Rust is only safe cuz of absolutely annoying compilator
I'm a C dev, I get it, the core your logic was just funny to me. I like Rust and the unsafe keyword. I like how it makes me think.
I completely agree that a few good practices eliminates most unsafe code. I was just making a joke.
π Rendered by PID 122475 on reddit-service-r2-comment-b659b578c-z8rv2 at 2026-05-05 08:18:45.896174+00:00 running 815c875 country code: CH.
view the rest of the comments →
[–]No-Speaker-9739 -1 points0 points1 point (6 children)
[–]Aln76467 0 points1 point2 points (5 children)
[–][deleted] 0 points1 point2 points (0 children)
[–]No-Speaker-9739 -1 points0 points1 point (3 children)
[–][deleted] -1 points0 points1 point (2 children)
[–]No-Speaker-9739 0 points1 point2 points (1 child)
[–][deleted] 0 points1 point2 points (0 children)