Matt: You're writing about two completely different things, thus the confusion. What we are discussing here as "interfaces" is referred to as "capsules" in that version of the spec. An "interface compilation unit" is, in effect, a header file. The term "interface" is unfortunately overloaded in the literature.
Jonathan On Mon, Jul 14, 2014 at 2:29 PM, Matt Rice <[email protected]> wrote: > something I suppose had me confused about the whole interface/guarded > interface topic is the relation (or non-relation as it may be) to type > constructors, > > from the bitc v0.10 spec "An interface compilation unit defines or > declares types > (and consequently the code of type constructors)", which IIRC means > that the declaration of a type exports implicitly a constructor for > that type. > > this, I believe differs from ML where you can export a type without > exporting a constructor for it. > > the ability to export a type, while exporting its constructor through > a guarded interface I find intriguing (albeit confusing as its not > something i've thoroughly explored), > > though it doesn't seem possible with the v0.10 implicit constructor > semantics, > since one can matador the guarded interface, and go directly for the > type constructor. it hasn't come up AFAICT, so i'm not sure if there > is any intention on revisiting this. > _______________________________________________ > bitc-dev mailing list > [email protected] > http://www.coyotos.org/mailman/listinfo/bitc-dev > >
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
