Hacker GitHub

← All repos

pizlonator/fil-c

View on GitHub ↗ ★ 3,898

Fil-C: completely compatible memory safety for C and C++

69 mentions on Hacker News by 48 people: 19 stories, 50 comments · first 2024-02-21 · latest 2026-10-27

Mentions per year 69 mentions · busiest year 2025 (36)
20082026
  1. ▲ 6
    Fil-C a memory-safe version of C and C++
    story by elromulous · 2024-11-16 · 1 comment
  2. …It’s not a new language, just a different way of implementing it. Here’s more info about Fil-C: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
  3. ▲ 3
    Fil-C: Memory-Safe and Compatible C/C++ with No Unsafe Escape Hatches
    story by emeryberger · 2024-10-24 · 4 comments
  4. I think it’s this: https://2024.splashcon.org/details/splash-2024-rebase/3/Fil-... https://github.com/pizlonator/llvm-project-deluge/blob/delug...
  5. A worked example: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by Rusky · 2024-10-16 · in The C23 edition of Modern C
  6. https://github.com/pizlonator/llvm-project-deluge
  7. https://github.com/pizlonator/llvm-project-deluge/blob/delug... https://m.youtube.com/watch?v=JRoX9_lXJFg Note that both that doc and the video have old perf numbers. I’m landing optimizations all the time.
  8. They do https://github.com/pizlonator/llvm-project-deluge/blob/delug... Or https://www.circle-lang.org/site/intro/
    comment by pizlonator · 2024-06-22 · in C can be memory safe
  9. I'm attempting something. https://www.youtube.com/watch?v=Gij9UQy_JEQ https://github.com/pizlonator/llvm-project-deluge/blob/delug... Right now I'm ~90% through a major rewrite to use GC instead of isoheaps, because then I'll go from…
    comment by pizlonator · 2024-04-04 · in Xr0: C but Safe
  10. …type at all. So one has to use indices everywhere. Why not just embrace isoheaps instead? [1] - https://github.com/pizlonator/llvm-project-deluge/blob/delug...
  11. …Why bother with Rust or any other language with borrow checkers then? Just a honest question. [1] - https://github.com/pizlonator/llvm-project-deluge/blob/delug...
  12. …people would like to run C code in the browser but don't want to bring memory unsafety there. link: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by fulafel · 2024-03-14 · in C++ Safety, in Context
  13. …use memory-safe OpenSSL. https://github.com/pizlonator/deluded-openssl-3.2.0 It's based on Fil-C https://github.com/pizlonator/llvm-project-deluge/blob/delug... There's no unsafe code in it. The whole thing is recompiled with Fil-C. Works…
  14. See here: https://github.com/pizlonator/llvm-project-deluge/blob/delug... I just got the OpenSSH client to work last night. Here's an example of the kinds of changes you have to make: https://github.com/pizlonator/deluded-openssh-portable/c…
  15. ▲ 2
    The Fil-C Manifesto: Garbage In, Memory Safety Out
    story by PaulHoule · 2024-02-25 · 0 comments
  16. ▲ 3
    Fil-C is a memory-safe compiler and runtime for C
    story by davikr · 2024-02-21 · 0 comments
  17. ▲ 3
    Fil-C: A memory-safe C compiler
    story by troberti · 2024-02-21 · 0 comments
  18. ▲ 2
    Fil-C: Memory-safe Compiler and Runtime for C
    story by awesomekling · 2024-02-21 · 1 comment
  19. ▲ 13
    The Fil-C Manifesto: Garbage In, Memory Safety Out
    story by Jarred · 2024-02-21 · 17 comments