From: Alain Frisch <alain.frisch@lexifi.com>
To: Anton Bachin <antonbachin@yahoo.com>,
Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] Bisect_ppx 1.0.0 – Modernized code coverage for OCaml
Date: Wed, 10 Feb 2016 22:49:24 +0100 [thread overview]
Message-ID: <56BBB064.9070505@lexifi.com> (raw)
In-Reply-To: <16829156-57F5-4517-8263-A367BB552732@yahoo.com>
On 10/02/2016 20:33, Anton Bachin wrote:
> Assuming this is what Gerd is indeed looking for, I can confirm that
> Bisect_ppx
> still supports it. See
>
> https://github.com/rleonid/bisect_ppx/blob/master/doc/advanced.md#unreachable-code
>
> We preferred to document only BISECT_VISIT (which does the same thing),
> in order
> to have only option. But both Bisect_ppx and Bisect support BISECT_MARK and
> BISECT_VISIT.
It's great to see the development of Bisect resurrecting!
Did you consider switching to attributes to mark code that must be
excluded from the analysis, instead of special comments? This seems
simpler than having to scan again the source files, and it could be more
robust when interacting with other ppx tools.
For instance:
- Marking a sub-expression, often using the shorthand syntax:
begin[@bisect.visit]
...
end
- Marking a complete function:
let f x =
...
[@@bisect.visit]
or (in OCaml 4.03):
let[@bisect.visit] f x =
...
- Marking sections:
[@@@bisect.visit.begin]
...
[@@@bisect.visit.end]
Alain
next prev parent reply other threads:[~2016-02-10 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 15:33 Anton Bachin
2016-02-10 16:46 ` David MENTRE
2016-02-10 19:27 ` Anton Bachin
2016-02-12 6:44 ` David MENTRÉ
2016-02-12 9:18 ` Anton Bachin
2016-02-10 19:00 ` Gerd Stolpmann
2016-02-10 19:23 ` Gabriel Scherer
2016-02-10 19:33 ` Anton Bachin
2016-02-10 21:48 ` Gerd Stolpmann
2016-02-10 21:49 ` Alain Frisch [this message]
2016-02-11 1:16 ` Anton Bachin
2016-02-11 10:42 ` Gerd Stolpmann
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=56BBB064.9070505@lexifi.com \
--to=alain.frisch@lexifi.com \
--cc=antonbachin@yahoo.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=info@gerd-stolpmann.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