TVL depot development (mail to depot@tvl.su)
 help / color / mirror / code / Atom feed
From: Vincent Ambo <tazjin@tvl.su>
To: Adam Joseph <adam@westernsemico•com>, depot@tvl.su
Subject: Re: reference-scanning inputDrvs/inputSrcs
Date: Tue, 10 Jan 2023 23:48:35 +0300	[thread overview]
Message-ID: <a69f3d4e-4a3a-96f8-9d18-9179aa518149@tvl.su> (raw)
In-Reply-To: <167338201858.17566.15445543013512077061@localhost>

On 1/10/23 23:20, Adam Joseph wrote:
> If I don't get it exactly right on the first try, tvix will get the blame
> for any behavioral differences, and that is not cool.

I think we have thick enough skin to deal with this ;) My plan is to go 
ahead anyways and implement this string-scanning based solution. We're 
fairly close to producing arbitrary derivation hashes, and as we're 
serialising derivations into the same format as C++ Nix we'll be able to 
use existing diff tools to figure out discrepancies when computing 
hashes over the whole package set.

I think this will allow us to figure out problems quite quickly! We can 
always resort to implementing string contexts if necessary.

> The implementation is straightforward and obvious except for placeholder > and unsafeDiscardOutputDependency

placeholders should fit into how we're envisioning the rest of the 
machinery pretty well, we'll see.

context discarding builtins are interesting, I have a working theory 
that the use-cases in which they are currently used simply do not apply 
in Tvix (and we can implement them as no-ops that emit warnings), and 
will probably write up another post about that.

> I have been dragged into a really enormous project that I have been wanting
> to do for a long time:
>
>    https://github.com/NixOS/nixpkgs/pull/209870

Cool to see work on bootstrap infrastructure. Hoping we can (in the not 
so far future) also collaborate with the Guix folks on that ...
Good luck with the project!

//V

      reply	other threads:[~2023-01-10 20:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANHrikrEDPkH1raGDGAGETeATrWOJ=sBQCUXr6=pHJm1ajbd0A@mail.gmail.com>
     [not found] ` <20221202152213.3a59e629@ostraka>
2023-01-09 22:07   ` [tvix] string contexts vs. reference scanning Vincent Ambo
2023-01-11 11:49     ` sterni
2023-01-11 12:20       ` Vincent Ambo
2023-03-16  9:41     ` Vincent Ambo
2023-03-16 12:00       ` Florian Klink
2023-01-10 20:20   ` reference-scanning inputDrvs/inputSrcs Adam Joseph
2023-01-10 20:48     ` Vincent Ambo [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a69f3d4e-4a3a-96f8-9d18-9179aa518149@tvl.su \
    --to=tazjin@tvl.su \
    --cc=adam@westernsemico$(echo .)com \
    --cc=depot@tvl.su \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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://code.tvl.fyi

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).