I want extern "fil-C"
ingve
21 points
3 comments
August 14, 2026
Related Discussions
Found 5 related stories in 39.7ms across 4,128 title embeddings via pgvector HNSW
- I want extern "fil-C" domenkozar · 53 pts · August 13, 2026 · 99% similar
- Introduce a memory safe compilation mode inspired by Fil-C mpweiher · 71 pts · July 20, 2026 · 51% similar
- Show HN: 18KB ls alternative in no_std rust and Libc tracyspacy · 22 pts · July 15, 2026 · 43% similar
- fx :Tiny, open, native coding agent. handfuloflight · 88 pts · August 18, 2026 · 40% similar
- Programming language file extensions that match ISO 3166-1 alpha-2 country codes speckx · 47 pts · July 24, 2026 · 39% similar
Discussion Highlights (3 comments)
my-next-account
Yeah, why not, ya know. Making your safe-ish C program slow and interoperable with Rust, in order to make people want to jump the boat to Rust. Us old-skool "unsafe? m0ar like skill issue" are gonna get left behind.
conradludgate
repost of https://news.ycombinator.com/item?id=49289260
tialaramex
For the fairly trivial cases I can see how this works. Rust constructs the appropriate Fil-C style shadow data at the ABI edges, fires some hooks, and there's some Fil-C compatible layer in Rust [like that introduced recently to provide FFI for variadic functions with a C ABI] in the other direction so your Rust can do the runtime checking Fil-C needs instead of the compile time checks Rust would expect. I think that's going to be a lot clunkier than typing `extern "fil-C"` in practice, but I can see how it would work. I think it chokes to death pretty quickly for a more sophisticated integration though because that clunk grows exponentially.