Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] Recursive classes and subtyping
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Frederic Tronel <Frederic.Tronel@i...>
Subject: Re: [Caml-list] Recursive classes and subtyping
> In the first case, the type "a" is not fully known when the coercion
> "(c :> a)" is performed, as the classes are mutually recursive.  The
> compiler handles this case as if it knew nothing about the structure
> of the type "a".  With this assumption, the only case the compiler can
> be sure that the type of "c" is a subtype of "a" is when the type of
> "c" is "a".  This is not the case, hence the error message.
> The reason for this overly conservative (in this case) assumption is
> that the result of the type inference algorithm could otherwise depend
> on the order in which the program is typed.

Clear !

> If you really need mutually recursive classes, a work-around is to
> explicitely define the classe types before defining the classes.

I don't really need recursive classes, but I started
writing my classes in a top-down manner with forward references to
to be defined. Hence, the use of recursive classes. I can simply change
my definitions order (bottow-up), it solves the problem !


Bug reports:  FAQ:
To unsubscribe, mail  Archives: