| 16 May 2024 |
 Qyriad | kill catch (...) with fire basically anywhere we can | 23:55:49 |
 delroth | I wonder what's the funniest parsing exception I could trigger which would lead nix to try and parse something as a flake | 23:56:46 |
| Qyriad | I want to fuzz that parser so badly | 23:57:04 |
 jade_ | fuzzing is cat behaviour | 23:57:20 |
 puck | | 23:57:52 |
| jade_ | puck: any opinions on choosing to intentionally leave the includes in their current location but still explode pkg-config and linking, vs also moving includes to lix/? | 23:58:46 |
| puck | move it. people should use pkg-config always even under nixpkgs | 23:59:06 |
| puck | or, hrm | 23:59:13 |
| puck | no, that'd break anyways | 23:59:18 |
| puck | i was thinking of the `foo -> <nix/foo> | 23:59:24 |
| puck | * i was thinking of the foo -> <nix/foo> thing | 23:59:25 |
| jade_ | yes, but lix/ includes do actually affect downstreams if they are including things via #include <nix/nixexpr.hh> | 23:59:30 |
| jade_ | but otoh we want to explode our include paths very aggressively in teh future anyhow | 23:59:51 |
| jade_ | so shrug | 23:59:53 |
| puck | symlinks :D | 23:59:57 |
| 17 May 2024 |
| jade_ | maybe the c api should be in nix/ still | 00:00:02 |
| puck | we can have compat pkg-config entries if we really care | 00:00:05 |
| jade_ | we should not have compat pkg-config | 00:00:14 |
| jade_ | because we don't have api compat | 00:00:18 |
| jade_ | we would just like to not explode peoples actual application code that badly for no reason i guess | 00:00:31 |
| puck | In reply to @jade_:matrix.org
maybe the c api should be in nix/ still oh, the C api is in the root of -isystem anyways; but i think we can discuss that; i might do a 1:1 with horrors about this some point soon | 00:01:01 |
| puck | (i'd like to get the C api in soonish because it'd mean we can run zilch on it) | 00:01:13 |
| puck | (mind you, https://puck.moe/git/zilch/tree/core/nix/default.nix?id=ae0f39a7b7eeef67442f96dd461648369fc47e0f#n3) | 00:01:34 |
| jade_ | anyway i guess im inclined to explode C++ API really hard on purpose. but we can stage the move include/nix/ to include/lix/ to a second change? idk what you prefer | 00:01:47 |
| puck | * (mind you, i miight've already done this~) | 00:01:51 |
| Qyriad | no one external is using the C API right now I'm not sure if it matters or not | 00:03:52 |
| puck | In reply to @puck:puck.moe
i think we'll likely break the C api but i have plans to try and convince robert (we can probably have a convincing point if we have a nice API and proper rust/python bindings) | 00:04:52 |
| delroth | anyway, https://gerrit.lix.systems/c/lix/+/1151 enough rabbit hole for tonight | 00:06:53 |
| delroth | also first bug I fix in Lix which is actually a Nix bug and not a regression in Lix /hides | 00:07:27 |
 julia | oh yeah for Gerrit if a change is all approved who presses the submit button? is it still one of the reviewers or is it supposed to be me | 00:13:19 |
