There's some work going on around batteries qtest program. See for instance
this wiki page on batteries tests:
https://github.com/ocaml-batteries-team/batteries-included/wiki/Developers-Guidelines
--
Caml-list mailing list. Subscription management and archives:
https://sympa-roc.inria.fr/wws
> - Chung-chieh Shan and Oleg's "Lightweight Static Capabilities"
> presents several examples of phantom types and a general design method
> to use them to enhance program safety:
> http://okmij.org/ftp/papers/lightweight-static-capabilities.pdf
I attempted to read this one out of curiosity,
a
> I often think the problem here is not with the code, nor the
> programmers, but with the tools. Editors should make it easier to
> fold scopes away and annotate the folded-away scopes with comments,
> when you don't want to directly look at the code.
Most editors do this, at least when the syn
> And if you don't want to pollute your entire code with functor when
> it's in fact for testing and not part of the logic of the application,
Functor seams the way to go here.
The use of this technique as envisaged here is hardly invading, and comes with
many advantages :
Functors help document
While comparing async and lwt you forget to mention performances. Didn't you
run any benchmark with some result to share ? Or are Async performances
irrelevant to your use cases so you never benchmarked ?
--
Caml-list mailing list. Subscription management and archives:
https://sympa-roc.inria.
