| 8 Mar 2024 |
|  @julienmalka:matrix.org joined the room. | 18:39:37 |
|  @janik0:matrix.org joined the room. | 18:55:10 |
|  jakegrin joined the room. | 19:30:57 |
|  rick.special joined the room. | 19:31:35 |
|  @me:indeednotjames.com joined the room. | 19:40:34 |
 @jade_:matrix.org | I just filed: https://github.com/NixOS/nixpkgs/pull/294353
In writing this I realized that we have both makeExtensible and makeScope. Is there any reason to use makeScope over makeExtensible? Have we written down somewhere secret which one to use in which cases? | 20:46:54 |
| @jade_:matrix.org | Related question: in things like the nix packaging, what is the best practice for exposing internals like the boehmgc-nix package while avoiding unnecessarily confusing users with bonus attributes they probably don't care about? https://github.com/nixos/nixpkgs/blob/9080c3655bf8094f99c8c7cb548fd0ee75928260/pkgs/tools/package-management/nix/default.nix#L17-L162 | 20:49:33 |
| @jade_:matrix.org | (specifically, I want to do a refactor where you can actually use the Nix common here from outside nixpkgs, which is currently not possible) | 20:50:11 |
 infinisil | In reply to @jade_:matrix.org
I just filed: https://github.com/NixOS/nixpkgs/pull/294353
In writing this I realized that we have both makeExtensible and makeScope. Is there any reason to use makeScope over makeExtensible? Have we written down somewhere secret which one to use in which cases? makeScope allows nested scopes to be created that somewhat compose | 20:50:29 |
| infinisil | That said, I don't think makeExtensible has any benefit over makeScope | 20:50:51 |
