From: ludo@gnu.org (Ludovic Courtès)
To: Amirouche <amirouche@hypermove.net>
Cc: help-guix@gnu.org
Subject: Re: Generalizing DAG rewriting
Date: Fri, 10 Feb 2017 10:55:22 +0100 [thread overview]
Message-ID: <87tw82gyk5.fsf@gnu.org> (raw)
In-Reply-To: <9e6855cb-d160-e6ba-e9f9-3c40a01a3162@hypermove.net> (amirouche@hypermove.net's message of "Fri, 10 Feb 2017 00:47:27 +0100")
Hi Amirouche,
Amirouche <amirouche@hypermove.net> skribis:
> Le 09/02/2017 à 10:55, Ludovic Courtès a écrit :
[...]
>> I agree that this is asking for generalization.
>>
>> Another instance of DAG rewriting is the ‘package-with-’ helpers in
>> (guix build-system gnu).
>>
>> We should have a general form of transformation procedure that handles
>> DAG traversal and memoization like all these procedures do.
>
> FWIW, I am very much interested in what you will come up with.
>
> How is different what you want to achieve from SXML Tree Fold [0]?
Here’s we’re dealing with DAGs, not just trees, so the notion of ‘up’
and ‘down’ doesn’t directly apply. But apart from that, we’re
essentially writing a combinator to traverse the DAG, which is similar.
> Wikipedia's graph rewriting [2] page cites a few softwares that deals with
> the issue along with some theory.
>
> [2] https://en.wikipedia.org/wiki/Graph_rewriting
>
> The place where I will need DAG rewriting is the replacement ReLeX (from
> opencog which AFAIK does graph rewriting somehow) and semantic/intent
> framing.
[...]
> WDYT of my rambling?
Heheh. :-) I think it’s interesting, but I’m not sure the actual
pieces of software you mention could be used here. At this point we
have fairly simple use cases, and a rewriting procedure like
‘package-input-rewriting’ is around 20 lines of code.
That said, there’s a need for generalized graph tools, and also tools in
(guix graph) that would allow us to get various graph metrics
efficiently (things like computing the “rank” of a node). So if you’re
into graphs you might be interested in fiddling with (guix graph) and
see what cool things could be done.
Thanks,
Ludo’.
prev parent reply other threads:[~2017-02-10 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 15:15 Recursively propagate build-system 'arguments' to dependency packages? Federico Beffa
2017-02-07 19:07 ` Myles English
2017-02-08 16:01 ` Ricardo Wurmus
2017-02-09 9:55 ` Generalizing DAG rewriting Ludovic Courtès
2017-02-09 23:47 ` Amirouche
2017-02-10 9:55 ` 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
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=87tw82gyk5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=amirouche@hypermove.net \
--cc=help-guix@gnu.org \
/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.
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).