From: HiPhish <hiphish@posteo.de>
To: guile-user@gnu.org
Subject: Re: A value for "nothing"
Date: Thu, 13 Sep 2018 23:49:10 +0200 [thread overview]
Message-ID: <8995890.4T62A8Hj0k@aleksandar-ixtreme-m5740> (raw)
After taking the advice from the mailing list users this is what I have come
up with:
(define-module (msgpack nil)
#:use-module ((srfi srfi-9) #:select (define-record-type))
#:export (nil? (get-nil . nil)))
(define-record-type nil
(make-nil) ; The raw constructor will not get exported
nil?)
(define get-nil ; This will be renamed on export
(let ((the-nil (make-nil))) ; Singleton instance
(λ ()
"- Scheme procedure: nil
Return the unique object representing nothingness in MessagePack.
All calls to this procedure return objects which are 'eq?' to each
other."
the-nil)))
The procedure `get-nil` gets exported as `nil` and returns a singleton
instance of my `nil` type. This way `(eq? (nil) (nil))` is always `#t`. The
only issues is that the `nil?` predicate collides with Guile's own `nil?`
predicate, so users will have to prefix or rename it when importing. I would
prefer not to export these two procedures with prefixes like `msgpack-nil` out
of the box, it's really ugly :/ What is the difference between `nil?` and
`null?` anyway? The former is not listed in the procedure index of the Guile
manual.
What do you think?
next reply other threads:[~2018-09-13 21:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 21:49 HiPhish [this message]
[not found] ` <CAD2gp_Sg-aDXZKfOcL-i2py7ne4c0Cp+2HvKS4DYi1Antm_B1A@mail.gmail.com>
2018-09-14 22:45 ` A value for "nothing" HiPhish
2018-09-15 0:26 ` John Cowan
2018-09-15 14:50 ` HiPhish
2018-09-15 18:28 ` Keith Wright
2018-09-15 21:50 ` Edwin Watkeys
2018-09-15 22:16 ` HiPhish
2018-09-15 22:23 ` Edwin Watkeys
2018-09-15 22:13 ` HiPhish
2018-09-15 22:45 ` David Pirotte
-- strict thread matches above, loose matches on Subject: below --
2018-08-26 20:25 HiPhish
2018-08-26 10:13 HiPhish
2018-08-26 17:21 ` Thomas Morley
2018-08-26 17:27 ` Joshua Branson
2018-08-26 17:49 ` John Cowan
2018-08-27 4:52 ` Mark H Weaver
2018-08-27 13:00 ` John Cowan
2018-08-27 21:29 ` Mark H Weaver
2018-08-27 21:32 ` Mark H Weaver
2018-08-26 20:07 ` Mark H Weaver
2018-08-26 22:08 ` Matt Wette
2018-08-27 8:04 ` tomas
2018-08-27 20:12 ` Mark H Weaver
2018-08-27 20:46 ` Mark H Weaver
2018-08-28 0:50 ` Matt Wette
2018-08-28 6:58 ` Mark H Weaver
2018-08-28 15:19 ` John Cowan
2018-08-28 15:38 ` Mark H Weaver
2018-08-28 15:59 ` Mark H Weaver
2018-08-28 16:12 ` John Cowan
2018-08-28 17:15 ` Mark H Weaver
2018-08-28 19:07 ` Mark H Weaver
2018-08-27 20:54 ` Hans Åberg
2018-08-27 0:17 ` Panicz Maciej Godek
2018-08-27 8:02 ` tomas
2018-08-27 8:29 ` Panicz Maciej Godek
2018-08-27 8:29 ` HiPhish
[not found] ` <8840615.kRvQfVdCvZ@aleksandar-ixtreme-m5740>
[not found] ` <CAD2gp_QLqd=_RbF=HTEbCLp1onmUq-c74g0FXTvMgdz8JB4-8A@mail.gmail.com>
2018-08-27 8:24 ` HiPhish
[not found] ` <3467110.H24gZIzStD@aleksandar-ixtreme-m5740>
[not found] ` <87ftz0vidc.fsf@netris.org>
2018-08-27 8:40 ` HiPhish
2018-08-27 12:37 ` Ludovic Courtès
2018-08-27 19:49 ` Mark H Weaver
2018-08-28 7:52 ` 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
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=8995890.4T62A8Hj0k@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=guile-user@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).