TSa wrote:
> HaloO,
>
> is this subject not of interest? I just wanted to start a
> discussion about the class composition process and how a
> role designer can require the class to provide an equal
> method and then augment it to achieve the correct behavior.
> Contrast that with the need to do th
Trey Harris wrote:
In a message dated Fri, 29 Sep 2006, Aaron Sherman writes:
That said, this is a different point, above and I think it's an easy
one to take on.
role A { method x() {...} }
class B { does A; }
does generate an error per "If a role merely declares methods without
defining t
Audrey (>), Carl (>>):
> Has this been settled or addressed off-list?
'fraid not yet...
Ah. So Warnock applies.
(Side note: when I first read "Warnock applies" on things in p6
summaries a year or so ago, I thought it was some really energetic
programmer who went around and applied patches as
在 Sep 28, 2006 3:03 AM 時，Carl Mäsak 寫到：
Audrey (>):
Indeed... Though what I'm wondering is, is there a hidden
implementation
cost or design cost of making /+/ always behave such that
$.from
returns something, compared to the current treatment with the
workaround
you suggested?
Has this
Jonathan Scott Duff wrote:
I hope you're way off the mark. Automatic coercion was one of the
annoyances I remember from C++. Debugging becomes more difficult when
you have to not only chase down things that are a Foo, but anything
you've compiled that might know how to turn itself into a Foo.
O
