| 2 Dec 2025 |
 emily | (ofc, not a good long-term solution to patch like that, but it's something that we could go to upstream about) | 01:58:37 |
 Randy Eckenrode | The guard isn’t in the swiftinterface. Either Apple strips it from their SDK build, or it doesn’t get put in there. | 01:59:29 |
| emily | yeah, I guess the guards are processed before generating the .swiftinterface. so making the compiler not immediately die when it sees a macro definition, and avoiding the .swiftinterfaces in favour of the source code when bootstrapping, are the two options there. | 02:00:25 |
| Randy Eckenrode | That works for Concurrency, but it doesn’t work for Foundation. | 02:00:34 |
| emily | well, they do have their FOSS Foundation, right? but yeah, making the macro definitions not immediately kill it seems like the easier thing to try. | 02:01:25 |
| Randy Eckenrode | Building swift-corelibs-foundation on Darwin isn’t really supported by upstream. | 02:02:55 |
| Randy Eckenrode | Their Swift-based Foundation is a subset of the full Foundation APIs. | 02:03:08 |
| Randy Eckenrode | I’m getting crashes in the compiler. The C++ bootstrap just isn’t ready for use yet. | 02:07:00 |
| Randy Eckenrode | Oh, neat. LLVM 16 was removed. That’s going to make building Swift 5.10.1 suck. Maybe I’ll just copy the existing derivation for bootstrap purposes. | 02:17:57 |
| Randy Eckenrode | Oh, right. It does wrapper crimes. | 02:19:16 |
 samasaur | it also doesn't work on linux at the moment | 02:19:40 |
| samasaur | https://github.com/NixOS/nixpkgs/issues/461474 or https://github.com/NixOS/nixpkgs/issues/462451 (i think they're the same issue) | 02:20:35 |
| emily | maybe a 6.2 binary might be an easier stopgap while the bootstrap compiler bakes | 02:22:15 |
| samasaur | if anybody has ideas about that issue, do let me know; it's entirely unfamiliar to me | 02:28:57 |
| Randy Eckenrode | I’m going to try applying https://github.com/swiftlang/swift/pull/83211. | 02:41:00 |
