On Wed, Jul 17, 2013 at 8:13 AM, Bennie Kloosteman <[email protected]>wrote:
> So the main problem case is large apps with lots of types... > Those may be a problem, but I don't think they are the main problem. The design risk in new features like trait instances and type class instances is that (a) they may turn out to get used but (b) the language design gets them wrong. Conversely, imperfect language features that people don't use aren't much of a problem in the field. The issue that concerned me in BitC was that type class instances were *very * close to ground (so *lots* of instances were going to get defined in various places for ground-related things, with a high likelihood of collision) and also very tightly interconnected with genericity. The second issue, when combined with a large number of ground value types, creates very strong pressure for overlapping instances, which in turn raise instance resolution problems. If all of this can be bounded to a single assembly, it becomes very manageable, so let me go start a new subject line. :-) Jonathan
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
