| 12 Jan 2026 |
 emily | if Swift pulls in SQLite regardless then maybe it's not worth trying to cut it out now | 18:23:06 |
 Randy Eckenrode | Then do Linux, but I think that will be okay with LLVM overrides being only somewhat broken now. | 18:23:07 |
| Randy Eckenrode | * | 18:23:26 |
| emily | are you at the point where you'd like broad architectural review for the Swift stuff btw? not sure what state that stuff has in, have been holding off on looking when there's no PR yet 😅 | 18:23:55 |
| emily | though of course my reliability at looking at stuff is less than I'd like in general lately… | 18:24:07 |
| emily | (will still try to look at that stdenv PR…) | 18:24:16 |
| Randy Eckenrode | I can push a branch where it’s just a big, mega commit. | 18:24:33 |
| Randy Eckenrode | I started over with my previous work as a base. | 18:25:03 |
| Randy Eckenrode | It’s doing things a bit differently. I found a way to make Lix stack overflow with bad recursion. 😂 | 18:25:51 |
| emily | oh dear | 18:26:10 |
| Randy Eckenrode | I accidentally had mutually recursive scopes. Whoops. | 18:26:20 |
| emily | yeah I figured the earlier I give annoying complaints about wild stuff the better :P | 18:26:42 |
| emily | very very excited for Swift Build though | 18:26:53 |
| emily | I am eager to drop xcbuild | 18:26:59 |
| Randy Eckenrode | It’s fixed now and more sensible. | 18:27:04 |
| Randy Eckenrode | Swift Build won’t be able to replace xcbuild unless we develop a driver. The swbuild CLI is too limited. | 18:28:22 |
| emily | 😔 | 18:28:47 |
