Hello!
Does anybody is involved in educational process (maybe in some
university)? I'm interesting what are typical graduation works?
Connected with ocaml, of course.
Best wishes,
Kakadu
--
Caml-list mailing list. Subscription management and archives:
https://sympa-roc.inria.fr/wws/info/caml-l
On Tue, Sep 20, 2011 at 12:26:15PM +0200, Gerd Stolpmann wrote:
> Am Montag, den 19.09.2011, 18:08 +0100 schrieb Richard W.M. Jones:
> > On Mon, Mar 28, 2011 at 04:03:09PM +0200, Gerd Stolpmann wrote:
> > > the ocaml team at Mylife is proud to release another library to the
> > > public: Netamqp is
Am Montag, den 19.09.2011, 18:08 +0100 schrieb Richard W.M. Jones:
> On Mon, Mar 28, 2011 at 04:03:09PM +0200, Gerd Stolpmann wrote:
> > the ocaml team at Mylife is proud to release another library to the
> > public: Netamqp is a client of the AMQP-0-9-1 protocol which is used to
> > talk to messag
For anyone who is interested, here is the bug report:
http://caml.inria.fr/mantis/view.php?id=5358
y
On Tue, Sep 20, 2011 at 6:07 PM, Yaron Minsky wrote:
> On Tue, Sep 20, 2011 at 5:03 PM, Alain Frisch wrote:
>
>>
>> The important point is that package types (the ... in a type expression
>>
Am Montag, den 19.09.2011, 13:09 -0700 schrieb Ian Zimmerman:
> I need a somewhat large (thousands) set of strings, created once during
> startup and never modified after. What is a better choice, a (string,
> unit) Hashtbl.t or the Set module? If the Set module still uses trees
> as it did when
On Tue, Sep 20, 2011 at 5:03 PM, Alain Frisch wrote:
>
> The important point is that package types (the ... in a type expression
> (module ...) or in an expression (module M : ...)) are not module types.
> Syntactically, they are indeed a subset of module types, but it is a strict
> subset, and th
For all of you wondering how unification works with package types:
(module Foo with type t1 = tau1 and type t2 = tau2 and ... and tn =
taun) unifies with (module Foo' with type t1' = tau1' and type t2' =
tau2' and ... and tn' = taun')
if and only if
n = n' and Foo = Foo' and t1 = t1' and t2 = t
On 09/20/2011 03:36 AM, Yaron Minsky wrote:
For some reason, 1st-class modules have more restrictive "with" syntax,
which turns out to be a practical problem.
The main constraint is that with constraints do not seem to be able to
refer to sub-modules. Consider the following code snippet:
I agree this works around the limitation, but it does beg the question: why
is the limitation there in the first place?
On Tue, Sep 20, 2011 at 4:00 PM, Jacques Le Normand wrote:
> first post! let's see if anyone can do better...
>
> module type Foo = sig type t end
> module type Bar = sig type f
first post! let's see if anyone can do better...
module type Foo = sig type t end
module type Bar = sig type foo_t module Foo : Foo type t = foo_t end
(* compiles *)
let g (type a) (m : (module Foo with type t = a)) = ()
(* fails to compile with a syntax error *)
let f (type a) (m :
10 matches
Mail list logo
