You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was talking to @puckipedia about this project and we were both somewhat surprised that Nix evaluations are invoked for each command invocation via nix-build on some Nix source, rather than emitting .drv files directly and skipping the nix language.
Emitting .drv files directly, then calling nix-store --add and nix-store --realise would save time and avoid the overhead of O(modules) number of Nix evaluations (although I do not have traces of exactly how much).
The text was updated successfully, but these errors were encountered:
This was always a plan of mine, but I skipped it because of the (minor) complexity of working out how to get a ghc derivation to depend on. We could probably do that with a single (constant) nix-instantiate though.
I was talking to @puckipedia about this project and we were both somewhat surprised that Nix evaluations are invoked for each command invocation via nix-build on some Nix source, rather than emitting
.drv
files directly and skipping the nix language.Emitting
.drv
files directly, then callingnix-store --add
andnix-store --realise
would save time and avoid the overhead of O(modules) number of Nix evaluations (although I do not have traces of exactly how much).The text was updated successfully, but these errors were encountered: