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

__curPos is not highlighted #132

Open
aciceri opened this issue Apr 23, 2024 · 1 comment
Open

__curPos is not highlighted #132

aciceri opened this issue Apr 23, 2024 · 1 comment
Labels
A-nameres Area: name resolution C-feature Catagory: feature good first issue Good for newcomers

Comments

@aciceri
Copy link

aciceri commented Apr 23, 2024

Notice that it's not a builtin but a keyword, I don't know where it should be added in the nil codebase. Also notice that probably there could be other keywords, it would be nice having a test or something that runs nix eval --expr "builtins.attrNames builtins" --json to check if we are considering all the builtins (if something similar isn't already done). I don't know if a similar introspection is possible also for keywords.

@oxalica oxalica added C-feature Catagory: feature good first issue Good for newcomers A-nameres Area: name resolution labels Nov 19, 2024
@lucasew
Copy link

lucasew commented Jan 7, 2025

__curPos in Nixpkgs is used as a implementation detail for something but nil treats its reference as a missing variable.

I want to eventually bring nil to nixpkgs as a ci step but this is a blocker as far as I know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-nameres Area: name resolution C-feature Catagory: feature good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants