all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 61214@debbugs.gnu.org
Subject: [bug#61214] [PATCH guix-artwork] website: posts: Add Dissecting Guix, Part 2: The Store Monad.
Date: Sun, 12 Feb 2023 20:38:45 +0000	[thread overview]
Message-ID: <CQGVH6E9HODC.145G6QF07H4IL@guix-framework> (raw)
In-Reply-To: <87h6vqlpxk.fsf_-_@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2582 bytes --]

Heya,

On Sun Feb 12, 2023 at 6:05 PM GMT, Ludovic Courtès wrote:
> Like Chris, I’m wary of acronyms (they can easily make things
> impenetrable) so I’d write:
>
>   - the `with-store` macro and the `run-with-store` procedure
>   - the related monad interface

Wow, I really did use 'API' quite a lot... Oops :)

> I agree with Chris’s comment: a few sentences of a higher-level intro
> showing where this fits in the big picture would be great!

Okay, I'll try to figure something out for that.

> It would be nice to stress, also, that one doesn’t _need_ to know about
> monads to use the various programming interfaces of Guix; instead, it’s
> a thing for someone who’d like to get a deep dive into the internals of
> Guix.

Fair enough :)

> Maybe add something like “For example, one might write a function that
> divides two integers such that it returns special value `nothing` when
> the divisor is zero, and `maybe 5` when passed `15` and `3`.”  (I
> couldn’t think of a better example but you get the idea.  :-))

Okay.

> > +feature of strongly-typed functional languages, and you'll see it all over the
>
> s/strongly/statically/  :-)

Ahh, that's why everyone was pointing out the wording :)

> In Scheme we use #f, not '(), to denote “Nothing”.

Mhm, not sure why I added '() in retrospect.

> Maybe “First, let’s import that module:”?

Too much 'API'... :)

> “To define a monad in Guix, we use `define-monad`”
>
> (In general, I’d avoid “simply” because whether it’s “simple” depends on
> one’s background.)

Ah, of course.  I should've remembered this from last time :)

> s/these laws/the so-called _monad laws_/

Good idea.

> Should it be “⇒ #t” instead of “;; #t”, to follow the convention used in
> the manual and in other places?

That's much nicer, yeah.

> s/monad API/monad module/ (or “monad library”)

(insert thumbs up emoji here)

> > +   strong types or an interface-like system.
>
> “static types”?

Yep.

> s/This API/The `(guix monads)` module/

Okay.

> Maybe link to the “The Store Monad” section of the manual here or
> earlier?

Oh, did I not link to it before, in the "Lies, Damned Lies, and Abstractions"
section!?

* unmatched-paren checks

...oops.

> I feel we’re asking a lot of work from you, but hopefully the result
> will be even more pleasant.  I guess v4 will be ready to go!

Hopefully! :)

> Thanks for all the work,

And thanks for all your own work! :)

    -- (

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-02-12 20:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 17:28 [bug#61214] [PATCH guix-artwork] website: posts: Add Dissecting Guix, Part 2: The Store Monad ( via Guix-patches via
2023-02-02  8:17 ` Simon Tournier
2023-02-02 13:06   ` ( via Guix-patches via
2023-02-02 15:00 ` [bug#61214] [PATCH guix-artwork v2] " ( via Guix-patches via
2023-02-02 15:04   ` ( via Guix-patches via
2023-02-06 15:38   ` Simon Tournier
2023-02-03  1:55 ` [bug#61214] run-with-state and run-with-store Feng Shu
2023-02-03  5:31   ` [bug#61214] [PATCH guix-artwork] website: posts: Add Dissecting Guix, Part 2: The Store Monad 宋文武 via Guix-patches via
2023-02-03  6:35   ` [bug#61214] run-with-state and run-with-store ( via Guix-patches via
2023-02-03  7:36 ` [bug#61214] [PATCH guix-artwork v3] website: posts: Add Dissecting Guix, Part 2: The Store Monad ( via Guix-patches via
2023-02-12 10:47   ` Christopher Baines
2023-02-12 14:17     ` ( via Guix-patches via
2023-02-13 12:08     ` zimoun
2023-02-12 18:05   ` [bug#61214] [PATCH guix-artwork] " Ludovic Courtès
2023-02-12 20:38     ` ( via Guix-patches via [this message]
2023-02-14  7:30 ` [bug#61214] [PATCH guix-artwork v4] " ( via Guix-patches via
2023-02-14  7:33 ` [bug#61214] [PATCH guix-artwork v5] " ( via Guix-patches via
2023-02-14 18:01   ` Simon Tournier
2023-02-14 19:26     ` ( via Guix-patches via
2023-02-16 17:00 ` [bug#61214] [PATCH guix-artwork v6] " ( via Guix-patches via
2023-02-20 21:23   ` Tobias Geerinckx-Rice via Guix-patches via
2023-02-20 22:04     ` ( via Guix-patches via

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=CQGVH6E9HODC.145G6QF07H4IL@guix-framework \
    --to=guix-patches@gnu.org \
    --cc=61214@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=paren@disroot.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.
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.