unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Timothy Sample <samplet@ngyro.com>
Cc: guile-user@gnu.org
Subject: Moving char-set->arbitrary into quickcheck proper?
Date: Thu, 25 Mar 2021 13:46:36 +0100	[thread overview]
Message-ID: <c469ea1e725f6e7ac036ecb5fabf708f95cda7eb.camel@telenet.be> (raw)

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

Hi,

Could the following procure from tests/kinds/octal.scm
in disarchive ...

<start snip>
(define (char-set->arbitrary cs)
  (arbitrary
   (gen (choose-char cs))
   (xform (lambda (chr gen)
            (generator-variant (char->integer chr) gen)))))
<end snip>

... be moved to guile-quickcheck?  (quickcheck arbitrary)
I find that procedure useful for testing some parser code.
For now, I've simply copied the code.

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

                 reply	other threads:[~2021-03-25 12:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c469ea1e725f6e7ac036ecb5fabf708f95cda7eb.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guile-user@gnu.org \
    --cc=samplet@ngyro.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.
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).