| 25 Jul 2021 |
infinisil | No need to convert to list first | 19:31:16 |
Jez (he/him) | Aha, thanks! Where on earth is that documented? I had to figure out the args with nix repl.. | 19:40:02 |
Jez (he/him) | * Aha, thanks! Where on earth is that documented? I had to figure out the args with nix repl... | 19:40:06 |
Andreas Schrägle | Jez (he/him): https://nixos.org/manual/nix/stable/ | 19:40:34 |
Andreas Schrägle |
builtins.substring start len s
| 19:40:41 |
Jez (he/him) | Ohhh, I was looking at https://nixos.org/manual/nixpkgs/stable/#sec-functions-library | 19:42:40 |
| 27 Jul 2021 |
| Guancha joined the room. | 19:15:50 |
| yusdacra joined the room. | 23:44:00 |
| 28 Jul 2021 |
| edlimerkaj joined the room. | 09:27:35 |
edlimerkaj | Hi everyone, I hope you all are doing great. I'm very new to this community and I'm not sure whether this is the right discussion to join to ask questions, but I'm giving it a try. I am currently trying to build a Go package and I'm trying to use buildFlagsArray, which from my understanding can be used to pass the same options as go build. Even though I'm not sure how to pass more than one option, so let's say "-X ..." and "-o ...". Is that possible? Also, can somebody please provide me with any explanation about the "-s" and "-w" options passed to buildFlagsArray. Thank you so much for your time in advance. | 09:27:41 |
infinisil | edlimerkaj: Also repeating here, this and #docs:nixos.org are the wrong place to ask, for help with nix/nixpkgs #nix:nixos.org is the right place. And besides this, don't post the same question in multiple channels at the same time, general chat etiquette 🙂 | 10:50:03 |
| shekhinah joined the room. | 14:59:56 |
| stuzenz joined the room. | 23:31:11 |
| 29 Jul 2021 |
| raghuram joined the room. | 18:06:01 |
infinisil | Weird feature request: Allow foo.bar..baz.qux = null, which is equivalent to foo.bar."".baz.qux = null | 20:25:17 |
infinisil | I don't even have a good reason. It's just that sometimes you need a way to define a "boundary" between arbitrarily nested attributes and structured ones | 20:25:58 |
sterni | this is probably parsed by -A correctly already, I could imagine | 20:26:22 |
infinisil | E.g. if you're trying to declare DNS records for domains, you'd want to do example.com..A.ip = "12.34.56.78" | 20:26:29 |
sterni | oh it explicitly checks for empty attribute names :( | 20:27:18 |
sterni | In reply to @infinisil:matrix.org E.g. if you're trying to declare DNS records for domains, you'd want to do example.com..A.ip = "12.34.56.78" OTOH there is probably little advantage in that over "example.com".A.ip except that it reads a bit nicer | 20:28:22 |
infinisil | sternenseemann: An advantage is that it gives merging behavior | 20:28:51 |
infinisil | Though I guess with DNS you'd want to go the other way, com.example..A.ip = ... | 20:29:17 |
infinisil | You could declare com.infinisil..A.ip below that, and it would merge to com = { example = ...; infinisil = ...; } | 20:29:43 |
sterni | yeah probably, or with ldap | 20:30:00 |
sterni | infinisil: the question is if you ever need an efficient lookup of either all domains that have the same name or the same tld in the nix eval | 20:31:33 |
infinisil | sternenseemann: Maybe it should be com..example.A.ip = "..." | 20:45:19 |
infinisil | Or `com..example..subdomain.A.ip = "..." | 20:45:30 |
infinisil | Or com..example..subdomain.A.ip = "..." | 20:45:38 |
infinisil | Then it's like the "" key indicates a nesting | 20:45:55 |
infinisil | Then you can also easily have com.A.ip = ... if you happen to be a TLD :P | 20:46:24 |