mirror of
https://github.com/privatevoid-net/nix-super.git
synced 2024-11-27 00:06:16 +02:00
65255edc9b
This does not yet resolve the coupling between packages and
derivations, but it makes the code more consistent with the
terminology, and it accentuates places where the coupling is
obvious, such as
auto drvPath = packageInfo.queryDrvPath();
if (!drvPath)
throw Error("'%s' is not a derivation", what());
... which isn't wrong, and in my opinion, doesn't even look
wrong, because it just reflects the current logic.
However, I do like that we can now start to see in the code that
this coupling is perhaps a bit arbitrary.
After this rename, we can bring the DerivingPath concept into type
and start to lift this limitation.
|
||
|---|---|---|
| .. | ||
| built-path.cc | ||
| built-path.hh | ||
| command-installable-value.cc | ||
| command-installable-value.hh | ||
| command.cc | ||
| command.hh | ||
| common-eval-args.cc | ||
| common-eval-args.hh | ||
| editor-for.cc | ||
| editor-for.hh | ||
| installable-attr-path.cc | ||
| installable-attr-path.hh | ||
| installable-derived-path.cc | ||
| installable-derived-path.hh | ||
| installable-flake.cc | ||
| installable-flake.hh | ||
| installable-value.cc | ||
| installable-value.hh | ||
| installables.cc | ||
| installables.hh | ||
| legacy.cc | ||
| legacy.hh | ||
| local.mk | ||
| markdown.cc | ||
| markdown.hh | ||
| nix-cmd.pc.in | ||
| repl.cc | ||
| repl.hh | ||