# How safe is zig?

**URL:** <https://forum.devtalk.com/t/how-safe-is-zig/8069>\
**Category:** Blogs/Articles/Talks/Podcasts\
**Tags:** rust, c-lang, zig, in-the-news\
**Created:** [22 March 2021 13:47 UTC](https://forum.devtalk.com/t/how-safe-is-zig/8069 "2021-03-22T13:47:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CommunityNews](https://forum.devtalk.com/user_avatar/forum.devtalk.com/communitynews/32/1113_2.png) [@CommunityNews](https://forum.devtalk.com/u/CommunityNews)\
**Post date:** [22 March 2021 13:47 UTC](https://forum.devtalk.com/t/how-safe-is-zig/8069/1 "2021-03-22T13:47:41Z")

</div>

> Like, on a scale from c to rust?

> | issue | c | zig (release-safe) | rust (release) |
> | --- | --- | --- | --- |
> | out-of-bounds heap read/write | none | runtime | runtime |
> | null pointer dereference | none | runtime | runtime |
> | type confusion | none | runtime, partial¹ | runtime² |
> | integer overflow | none | runtime | runtime³ |
> | use after free | none | none | compile time |
> | double free | none | none | compile time |
> | invalid stack read/write | none | none | compile time |
> | uninitialized memory | none | none | compile time |
> | data race | none | none | compile time |

[https://scattered-thoughts.net/writing/how-safe-is-zig/](https://scattered-thoughts.net/writing/how-safe-is-zig/)

_This thread was posted by one of our members via one of our news source trackers._