NixOS/nix
NixOS/nix
1
0
Fork 0
mirror of https://github.com/NixOS/nix synced 2024-10-18 14:32:45 -04:00
Code Activity
nix/doc/manual/src/language/constructs/lookup-path.md

28 lines
733 B
Markdown
Raw Normal View History

introduce lookup paths as a distinct language construct so far they did not really have a name, and were at best referred to as "angle bracket syntax".
2023-10-06 21:10:20 -04:00
# Lookup path
> **Syntax**
>
annotate admonitions showing syntax also fix typos
2023-10-09 18:32:36 -04:00
> *lookup-path* = `<` *identifier* [ `/` *identifier* ]... `>`
introduce lookup paths as a distinct language construct so far they did not really have a name, and were at best referred to as "angle bracket syntax".
2023-10-06 21:10:20 -04:00
docs: split types from syntax (#11013) move together all syntactic and semantic information into one page, and add a page on data types, which in turn links to the syntax and semantics. also split out the note on scoping rules into its own page. Co-authored-by: Ryan Hendrickson <ryan.hendrickson@alum.mit.edu>
2024-07-03 03:03:41 -04:00
A lookup path is an identifier with an optional path suffix that resolves to a [path value](@docroot@/language/types.md#type-path) if the identifier matches a search path entry.
introduce lookup paths as a distinct language construct so far they did not really have a name, and were at best referred to as "angle bracket syntax".
2023-10-06 21:10:20 -04:00
The value of a lookup path is determined by [`builtins.nixPath`](@docroot@/language/builtin-constants.md#builtins-nixPath).
See [`builtins.findFile`](@docroot@/language/builtins.md#builtins-findFile) for details on lookup path resolution.
> **Example**
>
> ```nix
> <nixpkgs>
>```
>
> /nix/var/nix/profiles/per-user/root/channels/nixpkgs
> **Example**
>
> ```nix
> <nixpkgs/nixos>
>```
>
> /nix/var/nix/profiles/per-user/root/channels/nixpkgs/nixos
Copy permalink