unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Blake Shaw <blake@sweatshoppe.org>, guile-devel@gnu.org
Subject: Re: [PATCH v1 1/6] docs/match: add pattern matching examples
Date: Sun, 29 Jan 2023 15:23:14 +0100	[thread overview]
Message-ID: <b0d4ff3b-3b0c-b3a9-7f94-b30444d179dd@telenet.be> (raw)
In-Reply-To: <CAKjmbcA9TeuC0HWE53cG4EfautTcW5s9tyh0tCXUvicAQiBFKQ@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1553 bytes --]



On 29-01-2023 03:40, Blake Shaw wrote:
> Hi Maxime,
> 
> Did you watch my talk from Guix days?

I read the text in the talk, but mostly skipped the speech.

> There I detailed that the goal 
> would be to move from what is painfully obvious, gradually building up 
> in chunks and peices. That is what is happening here.

OK, but I don't see the relevance of this information here.

> If you think the 
> progression of examples that follow are suboptimal in comparison to the 
> current state of the documentation, then you should give a reason why as 
> well as offer changes to be made.

I didn't say anything about the progression being good or bad.  I wrote:
>     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.

I.e., the example itself is suboptimal; the progression is presumably good.

Also, I did mention a reason why the example is bad: ‘this would be 
better done with 'case'’.  More explicitly, this example teaches to use 
'match' in situations where 'case' would be a better fit.

And I did offer changes to be made: ‘replace it with another example’
(I don't care which exact example it is replaced with, as long as its a 
simple example to fit in the progression and something where 'match' is 
actually a good fit in order to not teach suboptimal behaviour), and 
also gave an alternative, more explicit change 'add a note'.

Greetings,
Maxime.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  parent reply	other threads:[~2023-01-29 14:23 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
2023-01-28 19:23     ` randomlooser
     [not found]   ` <CAKjmbcA9TeuC0HWE53cG4EfautTcW5s9tyh0tCXUvicAQiBFKQ@mail.gmail.com>
2023-01-29 14:23     ` Maxime Devos [this message]
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=b0d4ff3b-3b0c-b3a9-7f94-b30444d179dd@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=blake@sweatshoppe.org \
    --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).