2023-06-22 Nix team meeting minutes #65

Attendees: @regnat @roberth @edolstra @fricklerhandwerk @Ericson2314

Agenda

  • Triage (30 min)
  • Triaging language-specific issues

Triage

https://github.com/NixOS/nix/pull/8519

Remove almost all noexcept annotations in src/libstore by Gabriella439 · Pull Request #6452 · NixOS/nix · GitHub

  • closed as already fixed

nix-daemon: Support socket-activated LaunchDaemon on macOS · Issue #5739 · NixOS/nix · GitHub

  • idea approved

remove maintainers checklist in PR template by fricklerhandwerk · Pull Request #8422 · NixOS/nix · GitHub

reword description of how realisation works by fricklerhandwerk · Pull Request #7592 · NixOS/nix · GitHub

Best effort supplementary groups by Ericson2314 · Pull Request #8342 · NixOS/nix · GitHub

  • idea approved but needs more work
  • assigned to @regnat

Language-specific issues

@roberth proposes to unblock other people’s work on language issues by filtering what would be worthwhile to deal with.

error "value is a list while a set was expected" is too vague · Issue #963 · NixOS/nix · GitHub

Adding an operator like Haskell's '$' · Issue #1845 · NixOS/nix · GitHub

  • closed, deferring to RFC process as this is has ecosystem-wide scope

Impossible to trace error: stack overflow (possible infinite recursion) · Issue #6361 · NixOS/nix · GitHub

  • this is a hard problem given the current language implementation
  • needs research for a reviewable implementation strategy

Unclear error message when a function is passed to `with` · Issue #934 · NixOS/nix · GitHub

  • idea approved

Provide a way to bind the argument set *including* default values · Issue #1461 · NixOS/nix · GitHub

  • closed, deferring to RFC 137 as this is has ecosystem-wide scope
3 Likes

I really appreciate these summaries, thanks for posting them!

Although to be honest, I read them as more of a “what interesting is happened in the Nix codebase this week”, rather than actually as meeting minutes as you’re probably intending them.

1 Like

These are meeting minutes, but it’s great that they are useful as an overview. The details on each discussion item are in the linked GitHub comments, as those are easier easier to retrieve in context when coming back to issues and PRs. Otherwise we record plans and decisions here, and strive to merge results into the repository documentation where they are easier to find.

2 Likes

Somebody with a bit more time and a bit more context could turn this into a nice little newsletter. cough hint

1 Like