| 21 Oct 2024 |
|  moved to @amadaluzia:tchncs.de changed their display name from (lambda (f l) (format nil "~a ~a")) "Artur" "Manuel" to (artur 'manuel). | 20:03:17 |
| 22 Oct 2024 |
|  @klaw:matrix.org joined the room. | 02:58:16 |
| @klaw:matrix.org left the room. | 02:58:34 |
|  human joined the room. | 04:49:35 |
|  @rnhmjoj:eurofusion.eu joined the room. | 09:23:11 |
| @rnhmjoj:eurofusion.eu left the room. | 09:23:53 |
 emhamm | In reply to @emhamm:matrix.org
Hey, i am trying to build nix.latest from master branch with enableDocumentation = false;.
This does not work, nix functional tests will call help.sh which will subsequently fail with: No manual entry for nix-build. Has anybody else run into this before? I prepared a fix, see https://github.com/NixOS/nix/pull/11729 - How do you guys handle backports? Should i create them for every affected version or is there an automatisation i did miss?
As it is my first PR feedback would be nice :-) | 09:52:02 |
| emhamm | In reply to @emhamm:matrix.org
Hey, i am trying to build nix.latest from master branch with enableDocumentation = false;.
This does not work, nix functional tests will call help.sh which will subsequently fail with: No manual entry for nix-build. Has anybody else run into this before? * I prepared a fix, see https://github.com/NixOS/nix/pull/11729 - How do you guys handle backports? Should i create them for every affected version or is there an automatisation i did miss?
As it is my first PR to nix feedback would be nice :-) | 10:07:47 |
 Robert Hensing (roberth) | emhamm: awesome. I've left a review - almost done. Backports are handled by mergify, which responds to GitHub labels. I'll set those, but if the automatic backport doesn't succeed, manual backports are much appreciated (just PRs to the <version>-maintenance branches) | 10:55:27 |
|  niko ⚡️ changed their profile picture. | 11:49:17 |
|  aktaboot changed their profile picture. | 12:10:58 |
|  Dylan changed their profile picture. | 17:00:02 |
|  @fernsehmuell:matrix.org set a profile picture. | 18:13:43 |
| 23 Oct 2024 |
|  @luna-null:matrix.org changed their display name from Autumn to luna-null. | 09:49:18 |
| @fernsehmuell:matrix.org left the room. | 19:11:39 |
| aktaboot changed their profile picture. | 19:53:57 |
|  Drewry Pope joined the room. | 20:58:47 |
| 24 Oct 2024 |
|  @nerves:bark.lgbt joined the room. | 02:20:24 |
 connor (burnt/out) (UTC-8) | Caveat to my question: I’m not as familiar as I’d like to be with this aspect of interpreters or implementations of languages, so apologies if it doesn’t make sense.
From my understanding of how lists and attribute sets are implemented, they are not persistent data structures (I remember seeing a lot of memory allocations followed by calls to memcpy). Is that correct?
If it is, is it possible persistent data structures could improve evaluation performance by allowing reuse? Or is it already known it would not, either due to other properties of the implementation (like GC behavior).
To be clear, I’m not implying that this should be a goal for the team — it’s more of a question in general about interpreted functional languages with a GC. | 16:59:01 |
|  Divesh joined the room. | 18:04:34 |
| 25 Oct 2024 |
|  lholh joined the room. | 03:53:31 |
