| 27 Jul 2025 |
 John Ericson | emily: well we don' | 16:51:52 |
| John Ericson | * emily: well we don't have to do 100% one or the oher | 16:51:59 |
| John Ericson | * emily: well we don't have to do 100% one or the other | 16:52:01 |
 emily | most of the benefits only happen when you 100% eliminate wrappers | 16:53:00 |
| emily | e.g. libclang used by Rust bindgen | 16:53:05 |
| emily | is inherently working with an "unwrapped compiler" and this causes issues | 16:53:13 |
| emily | and it is hard to be fully multi-target with wrapping | 16:53:33 |
| John Ericson | well I would rather make the investment in hopes we can someday get 100% | 16:54:00 |
| John Ericson | like, if we shoot to 100% in the first go, we may well die trying | 16:54:35 |
| John Ericson | but if we shoot for "as far as we can get before it gets too hard", and know we won't get to 100%, we can get to somewhere else without tears and budget overruns | 16:55:35 |
| John Ericson | and then we can later circle back, maybe in a later funding round when we have more budget on the basis of earlier successes :) | 16:56:24 |
| 28 Jul 2025 |
 Randy Eckenrode | And Swift’s built-in Clang driver. | 00:36:22 |
| Randy Eckenrode | I’m trying really hard not to use a wrapper with Swift. | 00:36:41 |
| Randy Eckenrode | * And Swift’s built-in Clang driver/importer. | 00:37:20 |
|  siraben joined the room. | 07:02:28 |
|  FireFly joined the room. | 08:48:56 |
|  Quentin joined the room. | 14:08:55 |
|  Guilherme Lima joined the room. | 20:30:15 |
| 31 Jul 2025 |
|  @unwary:matrix.org joined the room. | 00:24:26 |
| @unwary:matrix.org left the room. | 00:25:00 |
| 1 Aug 2025 |
|  Cathal joined the room. | 02:39:58 |
| 3 Aug 2025 |
 aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | https://github.com/NixOS/nixpkgs/pull/430575/files#diff-1ea2c8559b007cf7ff7861872d6572a11bdb8f6a5f41754cd8e424f7dac5bf5aR59 | 12:20:49 |
| aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | aarch64-linux gcc doesn't support c++20? | 12:21:04 |
| emily | nope, that's nonsense | 12:25:32 |
| emily | but the comment was already there | 12:25:46 |
| emily | it is just being moved around with formatting churn | 12:26:04 |
| emily | in this case the formatting churn goes around conventions, meta is generally not alphabetically-ordered | 12:26:14 |
| emily | and changelog before description and homepage is just weird | 12:26:37 |
| emily | nor do build inputs go after postPatch (there is no strict convention for all of this, but if you are going to do this kind of churn, explicitly making things comply less with the guidelines in https://github.com/jtojnar/nixpkgs-hammering/blob/b0817c8269798a830bc42f58a01c7543e7c5268a/explanations/attribute-ordering.md is hard to justify) | 12:27:32 |
| emily | so "bencode: sort" should be rejected, but checking and fixing the vintage broken comment is not a blocker | 12:28:00 |
