| 18 Dec 2025 |
 K900 | To see how much code those end up dropping | 13:22:36 |
 bake.monorail | what project are you talking about? nix?
is nix supposed to build with all the compilers in nixpkgs? I'm not saying that anything should build with it, just make the compiler available. | 13:23:08 |
| K900 | I'm talking about the cc-wrapper | 13:23:19 |
| K900 | Which is a component in nixpkgs that wraps compiler executables to make them behave the way we want | 13:23:35 |
| bake.monorail | to be honest I'd be happy to have older clangs even without the cc-wrapper, but I understand mine could be a niche use case. | 13:25:10 |
| bake.monorail | I'll take a look | 13:25:42 |
| bake.monorail | keeping old compilers building is not so hard, in my experience is just some new compiler error, nothing incredibly hard to patch. it's also useful for bootstrapping systems. I think it'd be valuable.
but yeah, it takes some effort. I'm curious about what features cc-wrapper needs. in my understanding it's just adding a bunch of compiler flags, but I didn't look too hard into it. | 13:29:04 |
 matthewcroughan | I mean, the reason anything would get dropped is because it's not working, so if you don't want to drop it you could just make PRs | 13:29:35 |
| bake.monorail | are you sure? AFAIU there's a policy about dropping end-of-life'd compilers. I don't think they necessarily "do not work" | 13:30:21 |
