Jonathan S. Shapiro wrote: > One problem with it is that it makes pre-expanding things for dynamic > libraries difficult, because we cannot anticipate the context from > which the function will later be called at the time we are compiling > the library.
Oh, for some reason I thought you were already specializing at link time. > Another possible confusion is that you can get situations where one > variable 'a is resolved by your caller in one context, and another 'b > is resolved in your own context, the two having the same constraint > specification but ending up with different instances because of the > different lexical contexts. > > Any inspiration on that? Do you have a concrete example I can mull over? > Unfortunately that isn't a good model, because the required vtable > cannot be build by any single caller. Are you referring to a multi-parameter type class where some type parameters are unknown? In this case, the instance would need to be selected from the set of possible choices once the type is supplied. typeclass Foo 'a 'b where testFoo: 'a -> 'b -> bool let doFoo: 'b -> bool = fun b -> testFoo 3 b Hmm, have to think about that. Sandro _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
