Hacker News new | ask | show | jobs
by dminik 8 days ago
I'm having a hard time squaring together two of the claims Andrew makes here:

- No source changes - https://codeberg.org/ziglang/zig/issues/36237#issuecomment-1...

- No escape hatches - main post

Surely there are already projects out there that rely on behaviours prohibited by Fil-C. One example that immediately comes to mind is reliance on external/C libraries.

Overall, I think adding it as a build target/ABI to the main compiler is pretty neat, but I do agree that it seems quite against the spirit of Zig (no hidden allocations, no hidden control flow). Combined with the combative title, I wonder how much of this is just "if I give them this, they will shut up about Rust."

1 comments

More like, we might shut up about use after free not being better than what C and C++ tooling has already provided for the last 30 years.

Also, Fil-C also makes use of GC technology, which is kind of ironic.