From: Simon Cruanes <simon.cruanes.2007@m4x.org>
To: "Christoph Höger" <christoph.hoeger@tu-berlin.de>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [qcheck] shrinking counterexamples on exception
Date: Thu, 30 Jun 2016 14:15:07 +0200 [thread overview]
Message-ID: <20160630121507.GG3637@nunchakus.loria.fr> (raw)
In-Reply-To: <e2e8f576-58f3-4a9b-cfd0-a277f2f532f1@tu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
Hi Christoph,
Please report on https://github.com/vincent-hugot/iTeML/issues !
Right now there is no shrinking on exceptions but it should be
possible (and reasonable) indeed.
--
Simon Cruanes
http://weusepgp.info/
key 49AA62B6, fingerprint 949F EB87 8F06 59C6 D7D3 7D8D 4AC0 1D08 49AA 62B6
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-06-30 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 12:11 Christoph Höger
2016-06-30 12:15 ` Simon Cruanes [this message]
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=20160630121507.GG3637@nunchakus.loria.fr \
--to=simon.cruanes.2007@m4x.org \
--cc=caml-list@inria.fr \
--cc=christoph.hoeger@tu-berlin.de \
/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 NNTP newsgroup(s).