unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: randomlooser@riseup.net
To: guile-devel@gnu.org
Subject: Re: [PATCH v1 1/6] docs/match: add pattern matching examples
Date: Sat, 28 Jan 2023 20:10:44 +0100	[thread overview]
Message-ID: <1f413ffbb8a33517bbe7366d6ffc1a569252922e.camel@riseup.net> (raw)
In-Reply-To: <259ecd49-6635-9426-394e-0b8064472615@telenet.be>

Il giorno sab, 28/01/2023 alle 14.18 +0100, Maxime Devos ha scritto:
> 
> 
> > +(define (english-base-ten->number name)
> > +  (match name
> > +    ('zero   0)
> > +    ('one    1)
> > +    ('two    2)
> > +    ('three  3)
> > +    ('four   4)
> > +    ('five   5)
> > +    ('six    6)
> > +    ('seven  7)
> > +    ('eight  8)
> > +    ('nine   9)))
> > +
> > +(english-base-ten->number 'six)
> > +@result{} 6
> 
> This is a suboptimal example; this would be better done with 'case'.
> I propose replacing it with another example, or adding a note that
> one 
> would normally use 'case' for this.

The point of this example is not to proficiently program in scheme

It is to introduce possibly naive people to pattern matching
effectively

The aim is to be didactic, there's no implication that this is
idiomatic scheme

I'd pay attention at the curse of knowledge that may be at play, here




  reply	other threads:[~2023-01-28 19:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 18:57 [PATCH v1 1/6] docs/match: add pattern matching examples Blake Shaw
2023-01-26 18:57 ` [PATCH v1 2/6] docs/match: rm unquote-splicing as it interferes with textinfo Blake Shaw
2023-01-27 16:27   ` Maxime Devos
2023-01-28  9:14     ` Blake Shaw
2023-01-28 13:08       ` Maxime Devos
2023-01-29  3:09         ` Blake Shaw
2023-01-26 18:57 ` [PATCH v1 3/6] docs/match: add reverse nested list example Blake Shaw
2023-01-26 18:57 ` [PATCH v1 4/6] docs/match: match-let* unwrap example Blake Shaw
2023-01-26 18:58 ` [PATCH v1 5/6] docs/fixup: @cindex was in the wrong place Blake Shaw
2023-01-26 18:58 ` [PATCH v1 6/6] docs/match:style reviewing with pdf, adding newlines Blake Shaw
2023-01-28 13:18 ` [PATCH v1 1/6] docs/match: add pattern matching examples Maxime Devos
2023-01-28 19:10   ` randomlooser [this message]
2023-01-28 19:23     ` randomlooser
     [not found]   ` <CAKjmbcA9TeuC0HWE53cG4EfautTcW5s9tyh0tCXUvicAQiBFKQ@mail.gmail.com>
2023-01-29 14:23     ` Maxime Devos
2023-01-28 13:48 ` Maxime Devos
     [not found]   ` <CAKjmbcAucYA9j7suY1gEAO512pn+90ED33Wq5Z7CjrBsqxgrbw@mail.gmail.com>
2023-01-29 15:30     ` Maxime Devos
2023-01-30  0:49       ` Blake Shaw
2023-01-30 19:56         ` Aleix Conchillo Flaqué
2023-01-30 19:57           ` Aleix Conchillo Flaqué
2023-01-31  2:53           ` Maxime Devos
2023-01-31  3:59             ` Aleix Conchillo Flaqué
2023-01-31  2:28         ` [PATCH v1 1/6] docs/match: add pattern matching examples + CoC Maxime Devos

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=1f413ffbb8a33517bbe7366d6ffc1a569252922e.camel@riseup.net \
    --to=randomlooser@riseup.net \
    --cc=guile-devel@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).