unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Stuart Hungerford <stuart.hungerford@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guile-user@gnu.org
Subject: Re: Idiomatic Guile for semigroup/monoid/group?
Date: Tue, 4 Jan 2022 08:02:23 +1100	[thread overview]
Message-ID: <CAG+kMrFfxbT91M+ki4Kc8vr3myTvYDqY6wawCJYdgCiL-8-PYQ@mail.gmail.com> (raw)
In-Reply-To: <8c869dfc519b7faeec5feabe9243efa25cd1668d.camel@telenet.be>

On Mon, Jan 3, 2022 at 9:14 PM Maxime Devos <maximedevos@telenet.be> wrote:

> Stuart Hungerford schreef op ma 03-01-2022 om 10:46 [+1100]:
> > Just out of interest, are there other multimethod/ad-hoc polymorphism
> > approaches for Guile?
>
> I only know of GOOPS and Theme-D -- Guix also has a
> ‘define-gexp-compiler’ but it's very ad-hoc.
>
> It allows defining something like
>
> (define (lower stuff system target)
>   (cond ((derivation? stuff) stuff) ; done
>         ((foo? stuff) (lower (lower-foo stuff system target)))
>         ((bar? stuff) (lower (lower-bar stuff system target)))
>         [...]))
>
> (where 'lower-stuff' converts 'stuff' into something 'lowerable'),
> but in an extensible way.

That's interesting -- thanks.

Stu



  reply	other threads:[~2022-01-03 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 23:45 Idiomatic Guile for semigroup/monoid/group? Stuart Hungerford
2022-01-02 10:46 ` Maxime Devos
2022-01-02 23:46   ` Stuart Hungerford
2022-01-03 10:14     ` Maxime Devos
2022-01-03 21:02       ` Stuart Hungerford [this message]
2022-01-03 10:02 ` zimoun

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=CAG+kMrFfxbT91M+ki4Kc8vr3myTvYDqY6wawCJYdgCiL-8-PYQ@mail.gmail.com \
    --to=stuart.hungerford@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=maximedevos@telenet.be \
    /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).