Am Fr., 3. Mai 2019 um 16:45 Uhr schrieb Arthur A. Gleckler
> On Tue, Apr 30, 2019 at 4:42 PM John Cowan <co...@ccil.org
>> In my opinion, the time has come to take the dictum "favor composition over inheritance" seriously, and not attempt to standardize inheritance, multiple or single for Scheme. The good part of OO is generic functions, and there is a proposal to include those (using predicates rather than classes) in R7RS-small. Googling "inheritance considered harmful|evil" will find a whole lot of explanations for what's wrong with implementation inheritance.
> I disagree. I don't want object-oriented inheritance, either, but simple data structure inheritance can be useful by itself, without the drawbacks of full OO inheritance. For example, in my implementation of hash array-mapped tries, used in SRFI 146, there are two record types that are structurally identical, i.e. that have the same fields, but that are used in different ways. It would be have made the code cleaner to have had them inherit their structure from a common type but still behave differently based on their subtypes. Composition would have been more verbose and would also have required an extra level of indirection and the associated cache misses in inner loops.