From: Chris Marusich <cmmarusich@gmail.com>
To: 26382@debbugs.gnu.org
Cc: Chris Marusich <cmmarusich@gmail.com>
Subject: bug#26382: [PATCH 0/3] Improve documentation for monads.
Date: Thu, 6 Apr 2017 02:15:46 -0700 [thread overview]
Message-ID: <20170406091546.24107-1-cmmarusich@gmail.com> (raw)
Hi,
The following patch series attempts to clarify how one is supposed to
use some of the monad-related syntax that Guix provides. It also
documents two commonly used forms (mwhen and munless) that were
missing from the manual.
Some of this might seem obvious to someone who is already familiar
with monads. However, since I only recently learned about monads, a
lot of these details were not obvious to me at all. For example, I
didn't know that every expression in an mbegin needs to be a monadic
expression (despite having read the manual multiple times). This was
especially confusing because the same is NOT true for an mlet. I hope
these patches will help clarify for other monad newbies how this
syntax is supposed to be used.
--
Chris
Chris Marusich (3):
monads: Use intent-revealing parameter names.
monads, doc: Improve mwhen and munless documentation.
monads: Improve mlet, mlet*, and mbegin documentation.
doc/guix.texi | 28 +++++++++++++++++++++++++---
guix/monads.scm | 36 +++++++++++++++++++++++-------------
2 files changed, 48 insertions(+), 16 deletions(-)
--
2.12.0
next reply other threads:[~2017-04-06 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 9:15 Chris Marusich [this message]
2017-04-06 9:28 ` bug#26382: [PATCH 1/3] monads: Use intent-revealing parameter names Chris Marusich
2017-04-06 9:28 ` bug#26382: [PATCH 2/3] monads, doc: Improve mwhen and munless documentation Chris Marusich
2017-04-08 12:31 ` Ludovic Courtès
2017-04-06 9:28 ` bug#26382: [PATCH 3/3] monads: Improve mlet, mlet*, and mbegin documentation Chris Marusich
2017-04-08 12:36 ` Ludovic Courtès
2017-04-08 12:30 ` bug#26382: [PATCH 1/3] monads: Use intent-revealing parameter names Ludovic Courtès
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=20170406091546.24107-1-cmmarusich@gmail.com \
--to=cmmarusich@gmail.com \
--cc=26382@debbugs.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.
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.