Post

Adding concurrency to Solod (a subset of Go that translates to C) felt great. But my favorite feature in the upcoming release is preventing the most common kind of dangling pointer: returning a pointer to a local variable from a function.

It's especially important to catch this, because it's perfectly valid in Go — but not in Solod, which has manual memory management. You can use a memory-unsafe language and still have some nice safety features.

0 reposts0 likes

No replies yet.