For example, the trait TPureBehavior has the method #<span style="font-family:courier new,monospace">traitComposition<span style="font-family:arial,helvetica,sans-serif">, which is an explicit requirement, and I can do</span></span><br>
I have that:<br><br><span style="font-family:courier new,monospace">(TPureBehavior&gt;&gt;#traitComposition) origin.� --&gt; TPureBehavior<br></span><br>which is nice.<br>Now lets suppose I create:<br><br><span style="font-family:courier new,monospace">Object subclass: #AAA</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">��� uses: TPureBehavior</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">��� instanceVariableNames: &#39;&#39;</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">��� classVariableNames: &#39;&#39;</span><br style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">��� poolDictionaries: &#39;&#39;</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">��� category: &#39;Guille&#39;</span><br><br>without creating the required traitComposition method<br><br><span style="font-family:courier new,monospace">(AAA&gt;&gt;#traitComposition) origin.� --&gt; AAA</span> ?????????? shouldn&#39;t the origin be TPureBehavior?<br>
<br><br>The question is:� Which is the intended behavior for the #origin of a method?� Because that&#39;s causing an issue in RPackage :).<br><br><br>I&#39;ve traced this, and it comes that if I have a trait method marked as explicitRequiriment, the following method answers just false <br>

<br>
<span style="font-family:courier new,monospace">CompiledMethod&gt;&gt;isProvided: marker</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">��� marker ifNil: [^ true].</span><br style="font-family:courier new,monospace">
<span style="font-family:courier new,monospace">��� ^ (self isRequired: marker) not and: [(self isDisabled: marker) not]</span><br>
<br>and then a magic <b>ifNone: [ self ]</b> return the receiver on the behavior, and that&#39;s why in both examples the method&#39;s behavior is returned instead of the origin.<br>Then we probably should have two methods<br>
�- #isProvided to see if an implementation is provided<br>�- #isDefined if a definition for the method exists<br>but those names do not make me happy.<br><br>Guille<br>