Traits explicitRequirement -- and TClassDescription
I'm not familiar with the #explicitRequirement I see sent in Slice 17798. Could someone explain why that is better than calling... self setName: aSymbol. Also, another thing I've been curious about for a while, what is the advantage of having TClassDescription when it only has one user ClassDescription? cheers -ben
On 26 Sep 2016, at 15:16, Ben Coman <btc@openinworld.com> wrote:
I'm not familiar with the #explicitRequirement I see sent in Slice 17798. Could someone explain why that is better than calling... self setName: aSymbol.
Traits donât have instance variables, so you somehow need to tell users to implement the methods that are supposed to write / read instance variables. Also, as traits are not classes, #subclassResponsibility isnât entirely correct semantically.
Also, another thing I've been curious about for a while, what is the advantage of having TClassDescription when it only has one user ClassDescription?
cheers -ben
I would like to remove traits users from metaclass class description. I do not think that they are worht hteh complexity they bring. Stef Le 26/9/16 à 16:16, Ben Coman a écrit :
I'm not familiar with the #explicitRequirement I see sent in Slice 17798. Could someone explain why that is better than calling... self setName: aSymbol.
Also, another thing I've been curious about for a while, what is the advantage of having TClassDescription when it only has one user ClassDescription?
cheers -ben
participants (3)
-
Ben Coman -
Max Leske -
stepharo