| 5 Mar 2024 |
 Jeremy Stucki | Can someone please open the door? It's locked and ringing the doorbells has no effect. | 17:03:58 |
 ners | Marc Jakobi | 17:04:11 |
| Jeremy Stucki | Hi guys, this is the package I'd like to get packaged:
https://github.com/NixOS/nixpkgs/issues/249155
Related issue:
https://github.com/NixOS/nixpkgs/issues/273668 | 17:28:57 |
| 6 Mar 2024 |
 Arialdo Martini | Hi folks. I really enjoyed the session together. As a person only working on Linux, Haskell and Nix exclusively in my free time (because work condemned me to awfully old technologies) I found you all really impressive and inspiring. Very energizing. Thank you! | 08:23:43 |
| Arialdo Martini | Yesterday you mentioned a way to use ghc to output the AST parsed from a Haskell source code. Would you be so kind to remind me again? | 09:49:32 |
| Arialdo Martini | In particular: I'm exploring the meaning of the jargon from type theory "above the arrow", "below the arrow" , "to the left of the arrow" when talking about forall and the fat arrow => | 09:51:56 |
| Arialdo Martini | * In particular: I'm exploring the meaning of the jargon from type theory "above the arrow", "below the arrow" , "to the left of the arrow" when talking about forall and the fat arrow => which I understand has to do with the position of forall in the syntax tree. | 09:52:29 |
| ners | In reply to @arialdo:matrix.org
Yesterday you mentioned a way to use ghc to output the AST parsed from a Haskell source code. Would you be so kind to remind me again? I remember talking about TH as a way to generate an AST that is then injected at the call-site.
To see the various intermediate representations that GHC generates in its various pipelines, you can use dump flags: https://downloads.haskell.org/ghc/latest/docs/users_guide/debugging.html
| 10:02:14 |
| ners | In reply to @arialdo:matrix.org
Yesterday you mentioned a way to use ghc to output the AST parsed from a Haskell source code. Would you be so kind to remind me again? * I remember talking about TH as a way to generate an AST that is then injected at the call-site.
To see the various intermediate representations that GHC generates in its various pipelines, you can pass it dump flags: https://downloads.haskell.org/ghc/latest/docs/users_guide/debugging.html
| 10:02:19 |
| ners | * I remember talking about TH as a way to generate an AST that is then injected at the call-site.
To see the various intermediate representations that GHC generates in its various pipelines, you can pass it dump flags: https://downloads.haskell.org/ghc/latest/docs/users_guide/debugging.html
In particular see section 5.13.1.1 for the AST.
| 10:02:59 |
| ners | 
Download image.png | 15:11:28 |
 das-g | In reply to @ners:nixos.dev
sent an image. Is that an invitation to the next Nix Zürich meetup, or just a shitpost. 🤔 | 20:48:13 |
| 8 Mar 2024 |
| ners | Just a meme. 🙃 | 08:37:04 |
| ners | @room I got confirmation for our next venue, just need to pick the date. Shall I aim for late March (3️⃣) or early April (4️⃣)? | 09:12:37 |
| ners | * @room I got confirmation for the next venue we can use for a meetup, just need to pick the date. Shall I aim for late March (3️⃣) or early April (4️⃣)? | 09:20:57 |
| 14 Mar 2024 |
|  NixOS Moderation Botchanged room power levels. | 18:44:24 |
| 16 Mar 2024 |
 Pablo Escodebar | fricklerhandwerk: https://github.com/escodebar/life/commits/nix/
I pushed the current iteration. It was fun 🤩 | 15:31:24 |
 fricklerhandwerk | I can recommend nix-unit btw, as it also allows catching exceptions. | 15:37:01 |
| Pablo Escodebar | I’ll clean up the repo at some point. I’ll push a branch for each programming language I implemented the game in. Previously it was just for an implementation in vue.js | 15:37:18 |
| Pablo Escodebar | I am pretty sure there are a couple on non-idiomatic parts. Would love to get some feedback. | 15:38:04 |
| Pablo Escodebar | All in all, I’m very happy to have done this (at least twice). Whenever I encounter nix code I’m now capable to read it and understand what is what 🥰 | 15:39:00 |
| fricklerhandwerk | I recommend to generally avoid import within files that are not at the very top level, especially of lookup paths like here: https://github.com/escodebar/life/blob/nix/life/rules.nix#L3
Use { lib }: ... - that makes your code a lot more reusable
| 15:42:35 |
| fricklerhandwerk | Also, put your top-level files (like flake.nix and default.nix) at the root of the repo, otherwise its a pain to actually call them | 15:43:37 |
| fricklerhandwerk | * Also, put your top-level files (like flake.nix and default.nix) at the root of the repo, otherwise its a pain to actually call them without manually cloning your repo | 15:43:45 |
| fricklerhandwerk | There's another, yet undocumented best practice: avoid using builtins directly and take the aliases from pkgs.lib. Nix cannot be reliably versioned, but Nixpkgs maintainers put a lot of effort into making library calls cross-version compatible | 15:46:56 |
| fricklerhandwerk | Otherwise looks reasonable. I'd factor and name a few things differently, but that comes with experience working on growing code bases. | 15:48:57 |
| Pablo Escodebar | Everyone: feel free to make pull requests with improvements and explanations of the improvements so I can further learn the language and the ecosystem 😊😘 | 15:52:35 |
| 19 Mar 2024 |
| NixOS Moderation Botchanged room power levels. | 00:29:50 |
| 21 Mar 2024 |
| Pablo Escodebar | fricklerhandwerk: thanks for the inputs. They started some discussions which made me learn and understand some conventions better. | 15:49:26 |
| Pablo Escodebar | Also, the exercise was really really worth it. I am so much more confident now when reading nix code. Previously I was totally overwhelmed, now, I can interpret nix code correctly. Can recomment my approach to learning nix to every beginner 😊 | 15:51:10 |
