Hi Sebastien,
I’m looking forward to your report, surely there will be some
interesting inspirations for us.
Am Montag, den 30.10.2017, 11:25 -0400 schrieb Edward Z. Yang:
> Actually, it's the reverse of what you said: like OCaml, GHC essentially
> has ~no unit tests; it's entirely Haskell
Excerpts from Sébastien Hinderer's message of 2017-10-30 16:39:24 +0100:
> Dear Edward,
>
> Many thanks for your prompt response!
>
> Edward Z. Yang (2017/10/30 11:25 -0400):
> > Actually, it's the reverse of what you said: like OCaml, GHC essentially
> > has ~no unit tests; it's entirely
Dear Edward,
Many thanks for your prompt response!
Edward Z. Yang (2017/10/30 11:25 -0400):
> Actually, it's the reverse of what you said: like OCaml, GHC essentially
> has ~no unit tests; it's entirely Haskell programs which we compile
> (and sometimes run; a lot of tests are for the
Actually, it's the reverse of what you said: like OCaml, GHC essentially
has ~no unit tests; it's entirely Haskell programs which we compile
(and sometimes run; a lot of tests are for the typechecker only so
we don't bother running those.) The .T file is just a way of letting
the Python driver
Dear all,
I am a member of OCaml's developement team. More specifically, I am
working on a test-driver for the OCaml compiler, which will be part of
OCaml's 4.06 release.
I am currently writing an article to describe the tool and its
principles. In this article, I would like to also talk about
