Open GoogleCodeExporter opened 8 years ago
Not sure that this is what we ought to do. subType(), like several other
methods in TypesBridge, basically provides a means of doing more complex
operations on one or two sequencetypes than the simple, required functionality
found in the type abstraction itself. In this case, implementation of subtype
basically iterates over the type inheritance tree, comparing each ancestor with
the target.
If we were to move subType(), would we not wish to move derivedFrom() ? That
one's more complex, because it asks the question about not only inheritance,
but about the form of inheritance. I do think that convenience methods, such as
this, probably belong outside the core of the type abstraction functionality.
Original comment by aale...@gmail.com
on 26 Jul 2012 at 7:29
Changed owner.
Original comment by eric%tib...@gtempaccount.com
on 6 May 2014 at 9:44
Original issue reported on code.google.com by
eric%tib...@gtempaccount.com
on 19 Sep 2011 at 1:09