| 30 Dec 2025 |
 @wolfgangwalther:matrix.org | From the interpreter side, all (known) issues with structuredAttrs should be solved since we bumped min version for Nixpkgs - we are not concerned anymore with any Nix versions that had problems there. structuredAttrs is certainly the way to go in the future, it's just a matter of time (and effort) to get the migration done.
The reason to support both with/without structuredAttrs is purely the transition period while not every expression supports them. This is mostly relevant for generic builders / setup hooks and such, which might not be able to tell in advance whether their downstream consumers will be using structuredAttrs or not.
The GHC expressions can certainly all be rewritten to consistently use structuredAttrs, no problem with that. Forcing the haskell generic builder to always use structuredAttrs would have an impact of out-of-tree users using that builder. If we're OK with a breaking change in that way, then yes, the best way is to consistently use structuredAttrs here, too. | 12:37:55 |
 maralorn | Is there some ressource about what structuredAttrs does and what it solves? | 12:53:28 |
 sterni | Nix manual I assume | 12:54:05 |
| @wolfgangwalther:matrix.org | https://nix.dev/manual/nix/2.19/language/advanced-attributes#adv-attr-structuredAttrs | 12:55:05 |
|  amadaluzia[tde] changed their profile picture. | 12:59:17 |
 linj | I find this blog very helpful https://nixos.mayflower.consulting/blog/2020/01/20/structured-attrs/ | 13:52:51 |
| sterni | We probably (also) have some new Haskell failures on master now with gcc15, so that may be worth checking up on in the coming days. | 18:32:11 |
|  Lenny. changed their display name from Lenny. ☎️5665 to Lenny.. | 23:09:43 |
