Rewrite docs for "Built-in Functions" #1048
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
awaiting
author
awaiting
contributors
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
Feature/S3
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix#1048
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The documentation for builtin functions is in a particularly messy state.
Some functions are well documented, some are missing half the features they have, for example
[fetchurl](https:// docs.lix.systems/manual/lix/2.94/language/builtins.html#builtins-fetchurl)is missing the entire description of the attribute set you could pass in.There is an additional problem that our syntax for parameters is inconsistent, does not allow for description of parameters "A ⊕ B" and does not allow for description of "attribute sets" well at all, which many of them take. This will require some rewrite of the generator for the PrimOps, but I believe this is worth it.
It may also be worth generating some form of index on the builtin functions as currently this is a very long document where it can be hard to find the part you need. The other option is to split it up, possibly by category, though this would be a discussion on it's own what those should be (suggestion, fetchers and string and path manipulation at least in their own sections each.)
We could split this up into two bugs, but they would be strongly related as the docs rewrite would show what the generator changes need to be.