From: "Ludovic Courtès" <ludo@gnu.org>
To: Philip McGrath <philip@philipmcgrath.com>
Cc: Ricardo Wurmus <rekado@elephly.net>, guix-devel@gnu.org
Subject: Re: better error messages through assertions
Date: Wed, 30 Mar 2022 11:37:10 +0200 [thread overview]
Message-ID: <87lewrwzll.fsf@gnu.org> (raw)
In-Reply-To: <c2e05e68-e2dd-67ab-4ae1-88b1e8adface@philipmcgrath.com> (Philip McGrath's message of "Mon, 28 Mar 2022 16:25:33 -0400")
Hi Philip,
Philip McGrath <philip@philipmcgrath.com> skribis:
> I'm thinking that a reasonable place to start might be to implement a
> `contract->sanitizer` form that would allow using contracts to create
> sanitizers, ideally with no changes to `(guix records)`.
OK. I’d prefer if people who define record types could directly write:
(field getter (contract integer/c))
rather than:
(field getter (sanitizer (contract->sanitizer integer/c)))
But that’s more of a detail.
> What is the preferred mechanism for exceptions?
For Guix code, SRFI-34/35.
> Likewise, what record system should I use?
SRFI-9.
(Perhaps we should put answers to these questions in the “Coding Style”
section of the manual.)
> Also, I don't know much about how the "abi" aspect of (guix records)
> works and what types of changes there would trigger rebuilds. (Though,
> again, I hope no changes would be needed for the proof-of-concept phase.)
I don’t think you need to worry about that.
> Another problem here seems to be the fault of (srfi srfi-9). For example:
[...]
> scheme@(guile-user)> (container-contents '())
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> In procedure struct-vtable: Wrong type argument in position 1
> (expecting struct): ()
>
> Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
> scheme@(guile-user) [1]> ,bt
> In current input:
> 3:0 1 (_)
> In ice-9/boot-9.scm:
> 1685:16 0 (raise-exception _ #:continuable? _)
> ```
>
> It seems like `container-contents` and other field accessors ought to
> check their arguments with `container?` (or the applicable predicate)
> and not leave error reporting to `struct-vtable`.
SRFI-9 generates the smallest amount of code for the job:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,use(srfi srfi-9)
scheme@(guile-user)> (define-record-type <foo>
(make-foo x)
foo?
(x foo-x))
scheme@(guile-user)> ,optimize (foo-x '())
$9 = (if (eq? (struct-vtable '()) <foo>)
(struct-ref '() 0)
(throw 'wrong-type-arg
'foo-x
"Wrong type argument: ~S"
(list '())
(list '())))
--8<---------------cut here---------------end--------------->8---
With Guile 3, it might be that adding an extra ‘struct?’ test would have
little effect on performance; we’d need to check.
> Perhaps this could be fixed in the (guix records) layer?
Could be, yes.
Thanks for looking into this!
Ludo’.
next prev parent reply other threads:[~2022-03-30 9:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 22:32 better error messages through assertions Ricardo Wurmus
2022-02-15 8:48 ` Maxime Devos
2022-02-15 21:45 ` Philip McGrath
2022-02-15 22:15 ` Ricardo Wurmus
2022-02-28 12:59 ` Ludovic Courtès
2022-02-28 16:18 ` Philip McGrath
2022-03-07 10:13 ` Ludovic Courtès
2022-03-28 20:25 ` Philip McGrath
2022-03-30 9:37 ` Ludovic Courtès [this message]
2022-03-30 13:28 ` Andy Wingo
2022-04-01 8:47 ` Ludovic Courtès
2022-04-01 19:28 ` Philip McGrath
2022-04-05 12:04 ` Ludovic Courtès
2022-04-01 19:47 ` Philip McGrath
2022-02-22 4:31 ` Arun Isaac
2022-02-25 18:55 ` Maxim Cournoyer
2022-02-26 13:33 ` Ricardo Wurmus
2022-02-26 13:51 ` Maxim Cournoyer
2022-02-28 13:02 ` Ludovic Courtès
2022-02-28 16:00 ` Maxim Cournoyer
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=87lewrwzll.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=philip@philipmcgrath.com \
--cc=rekado@elephly.net \
/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).