| 25 Oct 2024 |
|  @mel05saq:inphima.de set a profile picture. | 15:17:39 |
| 26 Oct 2024 |
|  vimfn joined the room. | 03:35:25 |
|  plmh joined the room. | 05:18:46 |
 Mic92 | connor (he/him) (UTC-7): that's also a hunch that I have. But I never tested/measured if it is true. I also found this library: https://sinusoid.es/immer/ which does even support boemgc (just like nix) | 09:01:05 |
| Mic92 | It shouldn't be too complicated to try it out for attrsets I think | 09:01:28 |
|  svrana left the room. | 15:51:41 |
| svrana joined the room. | 15:53:29 |
|  ubalot joined the room. | 16:05:09 |
|  Morgan (@numinit) left the room. | 23:46:30 |
| Morgan (@numinit) joined the room. | 23:47:43 |
| 27 Oct 2024 |
| Morgan (@numinit) set a profile picture. | 07:18:28 |
|  @rczb:envs.net joined the room. | 08:08:26 |
| @rczb:envs.net left the room. | 08:09:18 |
|  @jolly.roberts:matrix.org joined the room. | 15:19:15 |
| 29 Oct 2024 |
|  Samuel joined the room. | 03:18:06 |
 connor (burnt/out) (UTC-8) | I decided to start with lists hoping it’d be a smaller change
I have to say I don’t understand the rules governing lifetime of values
I also think the way Values are constructed (pointers and mutation) makes it difficult to use immer in an idiomatic way (at least, as far as I can infer from the docs)
At any rate, most of the tests pass so I’ll upload the work in progress hopefully today | 09:01:13 |
|  @docbrown101:matrix.org left the room. | 10:35:44 |
 tazjin |
I have to say I don’t understand the rules governing lifetime of values
the rule is "YOLO"
| 12:11:38 |
| connor (burnt/out) (UTC-8) | I don't know enough CPP to know if you're kidding lmao | 17:34:31 |
 K900 | That's the rule for all C++ code | 17:35:37 |
 @bjth:matrix.org | Redacted or Malformed Event | 18:49:16 |
| @bjth:matrix.org | Wrong channel, sorry. 🙃 | 18:54:38 |
|  eva changed their profile picture. | 22:26:41 |
| 30 Oct 2024 |
| connor (burnt/out) (UTC-8) | Design-wise, why does so much of libexpr take in pointers, mutate state, and return void? Is this "the way" interpreters or state management should be implemented when using C++?
To be clear, not criticizing! Just wanted to check if this pattern is one that just happened over the evolution of the codebase, is known to be a good way to do the implementation, or something else. | 00:19:11 |
|  Lach joined the room. | 00:25:02 |
 emily | it's a codebase from 2003 :) | 00:25:15 |
