| 26 Sep 2025 |
 Taeer Bar-Yam | is there a reason that in value.hh, we pass ptrSize around as a template variable, rather than using sizeof(void *) at the point of use, or defining static constexpr detail::ptrSize = sizeof(void *)? Do we ever want to instantiate things at multiple ptrSizes during the same compilation? | 13:10:28 |
| Taeer Bar-Yam | Never mind. I see there's some games being played to get it to specialize correctly for 32 and 64 bit systems. | 13:37:37 |
 John Ericson | who was going to work on the "deprecated features" thing? | 16:21:46 |
| John Ericson | * who was going to work on the "deprecated features" / "warnings" thing? | 16:21:52 |
| John Ericson | I want to disable absolute paths haha | 16:22:06 |
| John Ericson | * I want to disable absolute paths in the language, haha | 16:22:21 |
| John Ericson | Taeer Bar-Yam: I am curious whether you can remove std::string earlier in your ExprString PR commit history? | 16:55:13 |
| John Ericson | what is just stopping us from having the Value own it, and a std::string_view pointing within the value to avoid downcasting? | 16:55:42 |
| John Ericson | (perhaps this is something that Sergei Zimmerman (xokdvium) already talked to you about, in which case my bad) | 16:55:57 |
| John Ericson | is the issue that the value might be garbage collected too earlier / root set problems? | 16:56:33 |
| Taeer Bar-Yam | Yes. It will immediately get garbage collected | 16:56:59 |
| John Ericson | OK | 16:57:23 |
| Taeer Bar-Yam | probably I could rearrange the commits. I wasn't sure how much effort to put into cleaning up the commit history because i wasn't sure if I should squash them all before merging anyways | 16:57:47 |
 Sergei Zimmerman (xokdvium) | In reply to @shine:proqqul.net
probably I could rearrange the commits. I wasn't sure how much effort to put into cleaning up the commit history because i wasn't sure if I should squash them all before merging anyways In case the in-between commits are broken then there isn’t much point to keeping those separate. Also the diff is small enough | 16:58:45 |
| John Ericson | I don't know how much things can/should be squashed, I'll leave that to sergei :), but yeah anything that will be squashed away of course don't worry about the history | 16:59:06 |
| Taeer Bar-Yam | (i'm aware the tests are failing btw. looking into it) | 17:08:46 |
 Mic92 | Taeer Bar-Yam: btw. don't mind too much, but in general you can avoid "formatting" commands, by using git-absorb: https://github.com/tummychow/git-absorb | 18:25:51 |
| Mic92 | * Taeer Bar-Yam: btw. don't mind too much, but in general you can avoid "formatting" commits, by using git-absorb: https://github.com/tummychow/git-absorb | 18:25:59 |
| Taeer Bar-Yam | Ah, thanks for the tip! I'll try to look into it soon. Though I'm kind of wary of stuff that is automagical with my git history 😅 | 20:09:03 |
 magic_rb | It says it will only create fixup commits by default so you can review them | 20:10:29 |
| Taeer Bar-Yam | oh i see. that's much better | 20:10:55 |
| 27 Sep 2025 |
|  @meltymeli:catgirl.cloud joined the room. | 10:59:50 |
| @meltymeli:catgirl.cloud | Hi. I'm on Void Linux. I really like how Nix handles configuration, but am worried I have to hop to get the full experience. Is this the case? | 11:01:25 |
 K900 | The full experience being full system config, yes | 11:04:53 |
| K900 | Also wrong room kinda | 11:04:57 |
| K900 | You probably want #users:nixos.org | 11:05:05 |
| @meltymeli:catgirl.cloud | Thank you. Yes meaning I have to hop? | 11:06:22 |
| K900 | Yes meaning you have to run NixOS | 11:06:41 |
|  volth joined the room. | 18:40:20 |
| John Ericson | https://github.com/NixOS/nix/pull/14063 is ready for review | 19:13:31 |
