Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nix __dump-builtins does not include "derivation" #7753

Open
hsjobeki opened this issue Feb 4, 2023 · 2 comments
Open

nix __dump-builtins does not include "derivation" #7753

hsjobeki opened this issue Feb 4, 2023 · 2 comments
Labels

Comments

@hsjobeki
Copy link
Contributor

hsjobeki commented Feb 4, 2023

Describe the bug

As described in the title:
the nix __dump-builtins command does not include any information about the very fundamental "derivation" function of nix

Expected behavior

At least mention the function, or provide the same documentation as on all the other functions.

Priorities

Add 👍 to issues you find important.

@hsjobeki hsjobeki added the bug label Feb 4, 2023
@hsjobeki
Copy link
Contributor Author

hsjobeki commented Feb 4, 2023

@roberth can you maybe help me and assign it to the right person here ?

@roberth
Copy link
Member

roberth commented Feb 5, 2023

very fundamental "derivation" function

Seminal, not fundamental ;) The technical reason it's not included is because it's not defined as a regular primop, but rather a wrapper around the simpler and cleaner builtins.strictDerivation.

I don't think we need to care about __dump-builtins itself, an internal command, as long as the user-facing documentation and behavior are ok. I'd exclude the repl for now, because that's blocked on #1652 or a newer approach to that. Any other gaps in documentation can be filled.

@roberth can you maybe help me and assign it to the right person here ?

We can only assign to team members, and generally only for reviews and critical issues, as, considering the backlog, we have to allocate time effectively. We'll be happy to review contributions towards fixing this issue though, or to discuss the implementation strategy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants