- Original Message
> From: TSa (Thomas Sandlaß)
> > >> So what the OP wants to do is declare a method that is available on
> > >> all those invocants - and only those invocatnts - which do all of
> > >> roles X, Y, and Z. Granted, you can declare a new role XandYandZ
> > >> that does X
Author: moritz
Date: 2009-10-21 09:55:53 +0200 (Wed, 21 Oct 2009)
New Revision: 28868
Modified:
docs/Perl6/Spec/S06-routines.pod
Log:
[S06] more consistency on name collisions in signatures, masak++
Modified: docs/Perl6/Spec/S06-routines.pod
Author: masak
Date: 2009-10-21 10:50:10 +0200 (Wed, 21 Oct 2009)
New Revision: 28870
Modified:
docs/Perl6/Spec/S06-routines.pod
Log:
[S06] third attempt at describing elusive name collision
Modified: docs/Perl6/Spec/S06-routines.pod
=
On Wed, Oct 21, 2009 at 3:47 AM, Ovid
wrote:
> I was asking the special case where:
>
> 1. A class consumes two (or more) roles
> 2. Each roles provides a method with an identical signature
> 3. The methods are not equivalent and neither role can rely on the other's
> method
>
>
> With that, you
Ovid wrote:
I was asking the special case where:
1. A class consumes two (or more) roles
2. Each roles provides a method with an identical signature
3. The methods are not equivalent and neither role can rely on the other's
method
With that, you have roles which cannot be composed. You must
Jonathan Worthington wrote:
> Ovid wrote:
>>
>> I was asking the special case where:
>>
>> 1. A class consumes two (or more) roles
>> 2. Each roles provides a method with an identical signature
>> 3. The methods are not equivalent and neither role can rely on the other's
>> method
>>
>> With that,
Come, let us hasten to a higher plane
Where dyads tread the fairy fields of Venn,
Their indices bedecked from one to ''n''
Commingled in an endless Markov chain!
I'll grant thee random access to my heart,
Thou'lt tell me all the constants of thy love;
And
HaloO,
Jon Lang wrote:
I have some more thoughts on this; but I'm on a time crunch at the
moment, and would really like to get some feedback on the above before
proceeding further: have I missed anything in my reasoning?
I fully understand what you mean, I hope. But note that all instances
of
This is an automatically generated mail to inform you that tests are now
available in t/spec/S12-methods/what.t
commit b39906abb54f5c227e39afe5100ad41ba8ae60fc
Author: kyle
Date: Wed Oct 21 18:29:07 2009 +
[t/spec] Tests for RT #69915
git-svn-id: http://svn.pugscode.org/p...@
This is an automatically generated mail to inform you that tests are now
available in t/spec/S14-roles/composition.t
commit 8282341ffa5af1abb35a31d470184058a98c5009
Author: kyle
Date: Wed Oct 21 18:29:00 2009 +
[t/spec] Test for RT #69919
git-svn-id: http://svn.pugscode.org/p
This is an automatically generated mail to inform you that tests are now
available in t/spec/S02-names_and_variables/perl.t
commit c156c649e83b66ebc93d0cc114bd22c0d8fac772
Author: kyle
Date: Wed Oct 21 18:29:13 2009 +
[t/spec] Tests for RT #69869
git-svn-id: http://svn.pugsco
This is an automatically generated mail to inform you that tests are now
available in t/spec/S03-operators/smartmatch.t
commit 2843b387ac3dc7f896f1ab214b1cf4b5a2f2b235
Author: kyle
Date: Wed Oct 21 18:29:20 2009 +
[t/spec] Tests for RT #69762
git-svn-id: http://svn.pugscode.o
TSa wrote:
> Jon Lang wrote:
>>
>> I have some more thoughts on this; but I'm on a time crunch at the
>> moment, and would really like to get some feedback on the above before
>> proceeding further: have I missed anything in my reasoning?
>
> I fully understand what you mean, I hope. But note that
HaloO,
On Wednesday, 21. October 2009 12:40:06 Mark J. Reed wrote:
> Rather than disallow the composition, I'd say that any class, role, or
> object that does both roles must override the method in question.
The problem that Ovid posed needs to be resolved in the dispatch
tables seen in certain m
14 matches
Mail list logo
