| 12 Nov 2025 |
 raitobezarius | The NaN behavior unsoundness is unfortunate but we will have to document it and accept it. | 12:41:14 |
| raitobezarius | piegames if you have some time to spare, it'd be helpful for us if you can sign-off on https://gerrit.lix.systems/c/lix/+/4556 as well | 12:44:39 |
| raitobezarius | https://wiki.lix.systems/books/lix-contributors/page/pointer-equality contains exposition info | 12:44:47 |
 piegames | I'll try to have a look tomorrow | 13:14:27 |
 K900 | I picked a nit | 13:15:27 |
 niko ⚡️ | 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 | forgets this idea | 17:21:28 |
 aloisw | 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 | it's ~not but from an absolute PoV, it makes me so sad :D | 17:29:22 |
| raitobezarius | (_:O:[_]==[_]&&[_]!=O(_)[_])(_:_)map will be added to the iceberg | 17:29:44 |
| aloisw | Will the attrset update thing too, given that even the Snix folks missed it? | 17:32:23 |
