Maximilian Bosch ac48f07282 lib/types: always use <function body> instead of [function body] to indicate a function inside an option structure ... The motivation is to have a single identifier for that. Useful for the next commit where I'll try to escape option-parts correctly (options can be any kind of strings, but unless these are Nix identifiers, they must be quoted). Since `<function body>` (or `<name>`/`*`) are special identifiers in error messages and the manual, we need a unique way to mark an option part as function call because these are not to be quoted.		2022-10-07 10:01:44 +02:00
..
modules	lib/modules: Fix meta duplication in shorthand syntax	2022-09-21 10:55:11 +01:00
check-eval.nix
maintainer-module.nix	maintainer lib test: extract maintainer module	2022-06-20 22:20:26 +02:00
maintainers.nix	lib/tests/maintainers.nix: remove unused binding	2022-09-26 22:18:55 -04:00
misc.nix	lib: Add lazyDerivation	2022-09-21 10:55:07 +01:00
modules.sh	lib/types: always use <function body> instead of [function body] to indicate a function inside an option structure	2022-10-07 10:01:44 +02:00
release.nix	maintainer teams: check them in lib tests	2022-06-20 22:20:26 +02:00
sources.sh
systems.nix	lib/systems: add MicroBlaze architectures	2022-08-25 16:00:42 +02:00
teams.nix	maintainer teams: check them in lib tests	2022-06-20 22:20:26 +02:00