| 24 Feb 2026 |
emily | but I firmly believe attrNames set1 == attrNames set2 && attrValues set1 == attrValues set2 is the right semantics on both practical and theoretical grounds (and we should fix anywhere Nixpkgs still relies on pointer equality dodging type errors/aborts/throws/infinite loops and then move towards not doing that by default) | 15:51:51 |
piegames | Okay | 16:23:57 |
| 25 Feb 2026 |
| @kirottu:kirottu.com left the room. | 16:55:51 |
| isabel changed their profile picture. | 21:51:40 |
| 26 Feb 2026 |
| Lily Foster changed their profile picture. | 14:01:48 |
| n3tcat joined the room. | 23:44:11 |
| 27 Feb 2026 |
| find me at @lavender.pet:queer.sh changed their display name from lavender.pet to find me at @lavender.pet:queer.sh. | 20:14:32 |
| find me at @lavender.pet:queer.sh changed their profile picture. | 20:36:06 |
| 1 Mar 2026 |
| kylie changed their profile picture. | 03:25:03 |
| kylie changed their display name from somasis to kylie. | 03:52:40 |
Atemu | How is the lix command's -- supposed to function? Because when I do lix foo somearg -- otherarg, lix eats the -- and strips it from the args passed to lix-foo. It turns -vvvvv.. into -v -v ... too. | 11:43:02 |
Atemu | I'd have expected it to not touch any args after the subcommand | 11:44:22 |
Qyriad | Yeah I think that's a bug | 11:47:12 |
raitobezarius | that's because everything goes via the CLI parser | 11:48:21 |
raitobezarius | but we don't know yet if you are calling a subcommand | 11:48:26 |
raitobezarius | so you are receiving the CLI parser preprocessing which is discussable | 11:48:34 |
raitobezarius | please open a bug indeed with the info and we can take care of it | 11:49:07 |
| @hedy:envs.net removed their profile picture. | 14:36:23 |
| @hedy:envs.net left the room. | 14:36:23 |
piegames | sky1e: What are your plans for the Value outParam CLs? Will you migrate everything given enough time? (Though not sure if migrating all the primops would be a good idea …) | 14:58:43 |
sky1e | In reply to @piegames:flausch.social sky1e: What are your plans for the Value outParam CLs? Will you migrate everything given enough time? (Though not sure if migrating all the primops would be a good idea …) My intent is to ultimately work towards https://git.lix.systems/lix-project/lix/issues/744, and a major step of fixing all existing deprecated declaration usage is to remove all default constructions of Value | 15:36:49 |
sky1e | Out param functions can't be used without having an existing value to pass in, and usually that's default constructed | 15:40:27 |
piegames | So you're planning to also work on the OpenSSL deprecations etc. eventually? | 15:40:59 |
sky1e | I don't know, I haven't gotten that far. I figured incremental progress towards it would be helpful and appreciated for however long as I managed to stay focused on this task. It also depends on how hard the OpenSSL deprecations would be to fix. I don't know anything about them | 15:44:33 |
| @not-leader:envs.net removed their profile picture. | 19:58:39 |
| @not-leader:envs.net left the room. | 19:58:39 |
| 2 Mar 2026 |
| @rv32ima:envs.net removed their profile picture. | 07:13:22 |
| @rv32ima:envs.net removed their display name ellie. | 07:13:37 |
| @rv32ima:envs.net left the room. | 07:14:13 |
| Fernando Rodrigues joined the room. | 10:07:32 |