| 26 Apr 2024 |
|  Robert Hensing (roberth) changed the room topic to "Nix [C API](https://nixos.org/manual/nix/unstable/c-api), language-specific bindings, and their use cases" from "Nix C bindings (https://github.com/NixOS/nix/labels/c%20api), language-specific bindings, and their use cases". | 16:13:39 |
| Robert Hensing (roberth) changed the room topic to "Nix C API https://nixos.org/manual/nix/unstable/c-api, language-specific bindings, and their use cases" from "Nix [C API](https://nixos.org/manual/nix/unstable/c-api), language-specific bindings, and their use cases". | 16:14:01 |
| Robert Hensing (roberth) | Path values are represented by absolute paths, so I think that's what's expected by that function | 16:58:39 |
| Robert Hensing (roberth) | Not a great name, and insufficient docs though | 16:58:51 |
| Robert Hensing (roberth) | I think it needs to be improved: https://github.com/NixOS/nix/issues/10613 | 17:02:05 |
| 27 Apr 2024 |
|  pbsds joined the room. | 21:44:41 |
| 28 Apr 2024 |
|  kenji joined the room. | 09:59:50 |
| 29 Apr 2024 |
|  NixOS Moderation Botchanged room power levels. | 15:30:00 |
|  c4lliope joined the room. | 18:20:13 |
| 1 May 2024 |
| NixOS Moderation Botchanged room power levels. | 15:06:16 |
| 2 May 2024 |
|  Taeer Bar-Yam joined the room. | 15:10:51 |
| Robert Hensing (roberth) | Does anyone know a reason to use void * instead of opaque pointers like Value * (after struct Value;)?
I think we want to just change it: https://github.com/NixOS/nix/issues/10561 | 16:47:55 |
| Robert Hensing (roberth) changed the room topic to "Nix C API https://github.com/NixOS/nix/blob/master/doc/manual/src/c-api.md, language-specific bindings, and their use cases (currently broken link: https://nixos.org/manual/nix/unstable/c-api)" from "Nix C API https://nixos.org/manual/nix/unstable/c-api, language-specific bindings, and their use cases". | 17:19:16 |
|  thubrecht joined the room. | 17:21:25 |
|  Mindavi joined the room. | 17:44:58 |
|  Ilan Joselevich (Kranzes) joined the room. | 17:45:24 |
|  Las joined the room. | 17:52:59 |
|  Sergei Zimmerman (xokdvium) joined the room. | 17:56:38 |
|  Qyriad joined the room. | 18:18:05 |
|  Fernando joined the room. | 18:25:54 |
|  aciceri joined the room. | 18:33:38 |
|  Rickard Nilsson joined the room. | 21:17:56 |
|  Sigmanificient joined the room. | 22:21:14 |
| 3 May 2024 |
|  aloisw joined the room. | 04:23:01 |
|  Benedikt joined the room. | 17:53:10 |
|  Yingchi Long joined the room. | 21:17:07 |
| 4 May 2024 |
|  lukegb (he/him) joined the room. | 16:49:49 |
| 6 May 2024 |
|  l joined the room. | 11:21:23 |
| 9 May 2024 |
|  matrixuu joined the room. | 05:09:08 |
| 10 May 2024 |
 farcaller | is nix path supposed to always be absolute? i.e. is there any condition under which nix_init_path_string would allow a local path? the docs (https://sourcegraph.com/github.com/NixOS/nix@cb7224a8c2cc3aaee086d1e1ae539d7bb9a68915/-/blob/src/libexpr-c/nix_api_value.h?L316) don't specify that, but the only test (https://sourcegraph.com/github.com/NixOS/nix@cb7224a8c2cc3aaee086d1e1ae539d7bb9a68915/-/blob/tests/unit/libexpr/nix_api_value.cc?L115) checks the absolute path. Previously, the code would accept ./foo/bar as a valid path and return it as such. It doesn't, anymore.
I'd expect it to always resolve to absolute path (just like nix repl does), but then the logic of setting the rootFS (https://sourcegraph.com/github.com/NixOS/nix@cb7224a8c2cc3aaee086d1e1ae539d7bb9a68915/-/blob/src/libexpr/eval.cc?L400) evades me. How is that resolved in the bindings?
| 13:04:23 |
