Programming

17511 readers

236 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi

To kill memory safety bugs in C code, try the TrapC fork (go.theregister.com)

submitted 1 week ago by godiganbabay@ponder.cat to c/programming@programming.dev

2 comments fedilink hide all child comments

cross-posted from: https://rss.ponder.cat/post/57035

all 3 comments

sorted by: hot top controversial new old

[–] ulterno@programming.dev 5 points 1 week ago

Oh, how many times have I wished for a pointer to just null itself.
This one, depending upon how it gets implemented, should be a really good one.

[–] TehPers@beehaw.org 3 points 1 week ago* (last edited 1 week ago) (1 children)

There's a lot of bold claims being made. No segfaults, no memory leaks, etc. I'm curious to see how that's implemented.

Also:

it's safer than Rust because it lacks an "unsafe" keyword

lol