builtins generator: allow putting builtins into subsets #857
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
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
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#857
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?
One of the pieces of feedback that was regrettably blocking https://gerrit.lix.systems/c/lix/+/2975 is that adding a pile of bit builtins would further fill up the builtins namespace. Secondly we have a problem where builtins should really only be used by nixpkgs lib, at least for new builtins that should be used through a polyfill.
For example, we could have
builtins.bit.bitShiftLeft
.I don't know how to force the second, but we probably want the capability to namespace builtins anyhow. Maybe
builtins.privateForNixpkgsLibUseOnly
or something, which requires this anyway.This issue was mentioned on Gerrit on the following CLs: