From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: Feng Shu <tumashu@163.com>
Cc: 61214@debbugs.gnu.org
Subject: [bug#61214] [PATCH guix-artwork] website: posts: Add Dissecting Guix, Part 2: The Store Monad.
Date: Fri, 03 Feb 2023 13:31:28 +0800 [thread overview]
Message-ID: <87wn4zmi1b.fsf_-_@envs.net> (raw)
In-Reply-To: <87a61vtsuw.fsf@163.com> (Feng Shu's message of "Fri, 03 Feb 2023 09:55:51 +0800")
Feng Shu <tumashu@163.com> writes:
>> And to pass this initial state, we used `run-with-state`. The equivalent for working with
>> the store is our old friend `run-with-store`!
>
> For my poor English, I do not understand this well, does this mean
> "run-with-store will call run-with-state, we just use run-with-store
> generally." or "run-with-store is similer with run-with-state, they can
> replace each other"?
Well, "The equivalent for working with the store ..." should read as
"And to pass this initial store, we should use `run-with-store`".
> We can see that this `gexp->derivation` returns a procedure taking the
> initial state (store), just like our `%state-monad` procedures did.
> And to pass this initial state, we used `run-with-state`.
Maybe "And to pass the initial state for `%state-monad`, we used
`run-with-state`. So to pass the initial for `%store-monad`, we will
use `run-with-store`!" is better?
next prev parent reply other threads:[~2023-02-03 5:32 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 ` 宋文武 via Guix-patches via [this message]
2023-02-03 6:35 ` ( 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
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
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=87wn4zmi1b.fsf_-_@envs.net \
--to=guix-patches@gnu.org \
--cc=61214@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=tumashu@163.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).