| 6 Oct 2025 |
|  lovesegfault changed their profile picture. | 17:33:01 |
| lovesegfault changed their profile picture. | 17:33:46 |
 fzakaria | how do you build it with ASAN too? | 18:04:35 |
| fzakaria | oh i see it in doc | 18:05:55 |
| fzakaria | i was trying to build just 'debug' but i was hitting those FORTIFY_SOURCE warnings and build failures | 22:40:41 |
| fzakaria | would be nice to document how to get past that. | 22:40:48 |
 Sergei Zimmerman (xokdvium) | NIX_HARDENING_ENABLE=$(printLines $NIX_HARDENING_ENABLE | grep -v fortify) (ref eelco) | 22:42:38 |
| fzakaria | okay let me try that because debugoptimized | 22:43:59 |
| fzakaria | still skips stuff | 22:44:01 |
| Sergei Zimmerman (xokdvium) | ma27: thanks for the gdb fix btw. Very much appreciated to be able to use boost's pretty-printers out of the box. I hate how many hoops one has to jump through to get rid of -Wa,--compress-debug-sections though | 23:21:53 |
| 7 Oct 2025 |
| lovesegfault | could one reasonably write a nix evaluator without a GC and use refcounting, or would there be too many leaks due to cycles? | 04:07:54 |
 K900 | Definitely too many cycles without any form of GC | 04:16:48 |
| K900 | But you can probably get something out of refcounting compared to baseline | 04:17:27 |
| lovesegfault | that's a shame, i was thinking that conceptually it'd be nice to write an evaluator around rust futures | 04:17:31 |
| lovesegfault | but no gc there | 04:17:55 |
| K900 | That would be insanely inefficient tbh | 04:18:57 |
| K900 | Well, I guess it depends on how big your future state machine gets | 04:19:24 |
| K900 | But I'd expect it to get pretty big | 04:19:30 |
| lovesegfault | yeah idk how it play out, just seemed like something fun to try | 04:20:24 |
| lovesegfault | maybe if i used something like https://crates.io/crates/sdd | 04:24:06 |
