From: "Ludovic Courtès" <ludo@gnu.org>
To: ilmu <ilmu@rishi.is>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Deep vs Shallow trace: Removing the tradeoff?
Date: Tue, 30 Mar 2021 12:46:49 +0200 [thread overview]
Message-ID: <87blb0hqau.fsf@gnu.org> (raw)
In-Reply-To: <XuR-Ovr-FmTCISJzQZIxOdkzop1DWhD4bHddDL0DlelKnzKWuavLL-Rxl0_-Iq0Q0deg3nXiAkbovMchjneo6YSMH5pUzKQVcFYpkcV-emI=@rishi.is> (ilmu@rishi.is's message of "Sun, 28 Mar 2021 23:16:23 +0000")
Hi,
ilmu <ilmu@rishi.is> skribis:
> Early cutoff is a very desirable property that nix does not have (and I assume therefore that neither does guix).
The “intensional model” that Julien mentioned, or what the Nix folks now
refer to as “content-addressed derivations”, have this early cutoff
property. It’s one of the main motivations for this whole endeavors.
This document shows how Nix folks are working on retrofitting
“content-addressed derivations” into Nix:
https://github.com/tweag/rfcs/blob/cas-rfc/rfcs/0062-content-addressed-paths.md
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-03-30 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 16:56 Deep vs Shallow trace: Removing the tradeoff? ilmu
2021-03-28 0:50 ` Julien Lepiller
2021-03-28 23:16 ` ilmu
2021-03-30 10:46 ` Ludovic Courtès [this message]
2021-03-30 20:20 ` Bengt Richter
2021-04-02 15:45 ` ilmu
2021-04-17 15:05 ` Ludovic Courtès
2021-04-18 5:51 ` ilmu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blb0hqau.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ilmu@rishi.is \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).