| 21 Nov 2025 |
 Sergei Zimmerman (xokdvium) | Not exactly tho. jit/memory layout are tangential somewhat | 21:22:32 |
 Qyriad | yeah but you can optimize hot shapes | 21:22:56 |
| Sergei Zimmerman (xokdvium) | Yeah. I think python has slots for this kind of thing | 21:23:13 |
| Sergei Zimmerman (xokdvium) | * Yeah. I think python has __slots__ for this kind of thing | 21:23:28 |
 mzero | do you have something I could read about that? I'm curious how it would work. | 21:25:02 |
| Sergei Zimmerman (xokdvium) | Probably staring at prior art in V8? I haven't done that myself, but I'd be curious how they do tracing to find hot shapes | 21:26:04 |
| Sergei Zimmerman (xokdvium) | All of those optimizations are pretty inaccessible without tracing infra :( | 21:27:26 |
| Sergei Zimmerman (xokdvium) | But tracing attrset shapes doesn't exactly depend on function call tracing. Computing a shape fingerprint and having a small hashmap of that could give a rough picture of the frequency. | 21:29:23 |
| Sergei Zimmerman (xokdvium) | So maybe only do this for attrsets smaller than N, compute a hash of symbol table ids, store it a fixed-sized map and count frequency that way. This shouldn't have much of an overhead | 21:30:50 |
 John Ericson | yeah that is in a bitrotted PR | 21:39:29 |
| 22 Nov 2025 |
 helle (just a stray cat girl) | glares at lix/nix/prefetch.cc +118 | 11:47:29 |
| helle (just a stray cat girl) | erm, why are we making a presumption there, that uh, is not actually also made by nixpkg's fetchzip (which does have stripRoot as an active choice), this with certain use cases, like what npins does, makes it impossible to compute the right hash with it | 11:48:57 |
| helle (just a stray cat girl) | (anyway, I don't think it is worth a fix, because of well, yeah) | 12:06:43 |
|  adam joined the room. | 17:06:37 |
| helle (just a stray cat girl) | has anyone asked about https://docs.lix.systems/manual/lix/stable/contributing/deprecated-features.html#dp-feature-nul-bytes vs https://git.lix.systems/lix-project/lix/src/commit/7e193f962e35217268e81164eef9f8be7059a84e/doc/manual/rl-next/pascal-strings.md because we should figure out how to explain that one in documentation or uh, fix the situation as we now explicitly allow them | 20:18:51 |
| helle (just a stray cat girl) | also I think we need to rebuild all the Lix changelogs with anchors, I uh, may be in for some doing I guess, because having anchors is useful | 20:19:37 |
| helle (just a stray cat girl) | semi-related screams at the status of the Built-in Functions documentation uhhhh, we need to get some more intelligent arg handling and just combing through and writing all of it to the same standard and potentially some index gen | 21:03:19 |
| helle (just a stray cat girl) | given that I can't do much code rn, I may do some doc patches the coming week | 21:03:37 |
| helle (just a stray cat girl) | the doc/C++ generator for that also needs some work, so yeah.... | 21:05:18 |
| 23 Nov 2025 |
 piegames | In reply to @helle:tacobelllabs.net
has anyone asked about https://docs.lix.systems/manual/lix/stable/contributing/deprecated-features.html#dp-feature-nul-bytes vs https://git.lix.systems/lix-project/lix/src/commit/7e193f962e35217268e81164eef9f8be7059a84e/doc/manual/rl-next/pascal-strings.md because we should figure out how to explain that one in documentation or uh, fix the situation as we now explicitly allow them The nul-bytes deprecated feature is about nul bytes in the parser, which as of today still can cause truncation (in the parser, for non-indented strings), whereas the undefined behavior gotcha in terms of eval semantics is now indeed fixed | 07:32:11 |
| piegames | I hope that makes sense | 07:32:16 |
| helle (just a stray cat girl) | In reply to @piegames:flausch.social
The nul-bytes deprecated feature is about nul bytes in the parser, which as of today still can cause truncation (in the parser, for non-indented strings), whereas the undefined behavior gotcha in terms of eval semantics is now indeed fixed I mean I read the code and tests to figure it out (after filing the bug, should ammend it), it made total sense, but if you are not diving that deep, the docs need to be specific enough to explain what is going on there as initially it looks like a conflict | 07:40:12 |
| piegames | If you can tackle fixing that that would be appreciated | 09:30:50 |
| helle (just a stray cat girl) | okay, will tag you on the patch as I need to make sure to word it right | 09:35:37 |
| 16 May 2024 |
|  zrsk joined the room. | 13:54:49 |
 samrose | In reply to @lunaphied:lunaphied.me
I think there were a few CLs on the Gerrit but nothing being actively worked The other thing that I could do if it helps is test things and try to find bugs. I did do some C++ work in the past, but may lack the time to do it justice here at least for about 30 days or so | 15:55:29 |
| Qyriad | we are not in any rush 🙂 | 17:20:53 |
| samrose | Would it help to also test out the existing Lix code and try to find issues/bugs etc? | 17:23:21 |
| Qyriad | absolutely | 17:23:41 |
| samrose |
- how do people feel about the existing test suite that comes along with nix source code or Lix?
| 17:23:48 |
