!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

410 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.136 Servers

Load older messages


SenderMessageTime
12 Nov 2025
@raitobezarius:matrix.orgraitobezarius https://wiki.lix.systems/books/lix-contributors/page/pointer-equality contains exposition info 12:44:47
@piegames:flausch.socialpiegamesI'll try to have a look tomorrow13:14:27
@k900:0upti.meK900I picked a nit13:15:27
@niko:nrab.lolniko ⚡️
In reply to @raitobezarius:matrix.org
The NaN behavior unsoundness is unfortunate but we will have to document it and accept it.
Cursed not really serious idea - do pointer comparison as doubles, and make any object pointer which contains a nan, nan itself, and everything else not nan
13:33:45
@raitobezarius:matrix.orgraitobezarius forgets this idea 17:21:28
@aloisw:julia0815.dealoisw Is it worse than before? My understanding is that the only change for NaN is that after attrset update it will now sometimes return false (similar to the load-bearing change that was observed for functions, but hopefully less load-bearing there). 17:28:55
@raitobezarius:matrix.orgraitobezariusit's ~not but from an absolute PoV, it makes me so sad :D17:29:22
@raitobezarius:matrix.orgraitobezarius (_:O:[_]==[_]&&[_]!=O(_)[_])(_:_)map will be added to the iceberg 17:29:44
@aloisw:julia0815.dealoisw Will the attrset update thing too, given that even the Snix folks missed it? 17:32:23
@raitobezarius:matrix.orgraitobezariusit shall be17:32:35
@raitobezarius:matrix.orgraitobezarius:D17:32:37
@raitobezarius:matrix.orgraitobezariusin other news17:32:47
@raitobezarius:matrix.orgraitobezariusthe Value changes creates this noticeable evaluation changes17:33:02
@raitobezarius:matrix.orgraitobezarius
android32.rustc.x86_64-linux changes error message significantly (was unfree, now is unsupported)
x86_64-freebsd.cargo.aarch64-darwin goes from unsupported to broken
x86_64-netbsd.buildPackages.binutils.aarch64-darwin evals (was infrec)
x86_64-netbsd.cargo.aarch64-darwin is broken (was infrec)
x86_64-netbsd.gmp.aarch64-darwin evals (was infrec)
x86_64-netbsd.libc.aarch64-darwin same
x86_64-netbsd.mesa.aarch64-darwin unsupported (was infrec)
x86_64-netbsd.nix.aarch64-darwin evals (was infrec)
x86_64-netbsd.nixVersions.git.aarch64-darwin same
x86_64-netbsd.rustc.aarch64-darwin same
17:33:06
@raitobezarius:matrix.orgraitobezariuswe deem this an improvement17:33:15
@raitobezarius:matrix.orgraitobezariusbut we also discovered outPath changes17:33:26
@raitobezarius:matrix.orgraitobezarius(which is the "uh-huh" moment)17:33:40
@raitobezarius:matrix.orgraitobezarius* the Value changes creates these noticeable evaluation changes17:33:54
@raitobezarius:matrix.orgraitobezarius my personal explanation is that the sharing broke cycles in the evaluation expression graph, so we can do more 17:34:08
@raitobezarius:matrix.orgraitobezariusthe test is 2.93 → post-CL change17:34:16
@raitobezarius:matrix.orgraitobezarius(this is done from the release-cross.nix file)17:34:40
@raitobezarius:matrix.orgraitobezariusok17:35:13
@raitobezarius:matrix.orgraitobezariusguessing time17:35:15
@raitobezarius:matrix.orgraitobezariusclipboard.png
Download clipboard.png
17:35:16
@raitobezarius:matrix.orgraitobezarius(the outPath alert was a false alarm but guess why just by reading this diff)17:35:27
@raitobezarius:matrix.orgraitobezarius(and then hate nixpkgs)17:35:35
@aloisw:julia0815.dealoisw How on earth does this work in pure mode to begin with? 17:36:55
@raitobezarius:matrix.orgraitobezariusi have no idea :D17:37:22
@raitobezarius:matrix.orgraitobezariusbut this is fucking cursed code that has been accepted in nixpkgs17:37:34
@raitobezarius:matrix.orgraitobezarius i think nixpkgs CI doesn't run in pure mode actually? 17:37:44

Show newer messages


Back to Room ListRoom Version: 10