all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 51021@debbugs.gnu.org
Subject: bug#51021: detect loops in module/package graph
Date: Tue, 12 Oct 2021 11:47:39 +0200	[thread overview]
Message-ID: <87czoawp50.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ2RA3en1f2VirYFJakrHMashyE24J5wevq_pEmyd=-dDg@mail.gmail.com> (zimoun's message of "Mon, 11 Oct 2021 09:49:00 +0200")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> What Mark had implemented [1] works for any directed graph.  What do
> you mean by "top-level references"?

Reference to variables coming from one module of an SCC that appear at
the top level of another module in the SCC.

>> Chris Baines proposed a patch a while back to report those, though I
>> can’t find it anymore.  IIRC, the difficulty was in making sure cycle
>> detection would not be too expensive, and in keeping a readable style.
>
> From my memories about Graph Theory, the algorithm Mark is proposing
> is an efficient way to detect cycles

What I meant is that ‘package-derivation’ traverses the package graph,
so it’s a natural place to add cycle detection.

But since ‘package-derivation’ is so central, care must be taken about
the performance hit and about its readability.

Thanks,
Ludo’.




      reply	other threads:[~2021-10-12  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05  0:58 bug#51021: detect loops in module/package graph raingloom
2021-10-05  7:59 ` Mark H Weaver
2021-10-05  8:03   ` Mark H Weaver
2021-10-07 13:28   ` Ludovic Courtès
2021-10-11  7:49     ` zimoun
2021-10-12  9:47       ` Ludovic Courtès [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=87czoawp50.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=51021@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.