four chains of subtypes A to G, A to H
via E and F, and A to I. Within these chains the methods are comparable
for specificity. I don't know if this is what is meant by "type
compatibility path" in mmd-draft.txt.
For writeonly parameters the partial order extends in the other
directi
HaloO,
I have one further question to the document. It mentions
chains of type coercions that are applied in the compatibility
stage. A type that has fewer conversion steps is considered
more specific. But is that a wise thing to do in an MMD system?
I would expect no coercions to occur. How can
HaloO,
Audrey Tang wrote:
> A variant's score cards only records two Boolean values for each
> variant: "voting" and "qualified".
Here is a summary of the explanation Audrey gave me on #perl6.
Note that this is from memory because I didn't save the log.
In particular I don't remember exactly whe
在 Oct 26, 2006 10:26 AM 時，TSa 寫到：
I figure that
http://svn.openfoundry.org/pugs/docs/notes/multi_method_dispatch/
mmd-draft.txt
hasn't made it into S06 yet. So what is the current state of affairs?
The original plan was to have Larry review it in Brazil and check it
in along wi
HaloO,
I figure that
http://svn.openfoundry.org/pugs/docs/notes/multi_method_dispatch/mmd-draft.txt
hasn't made it into S06 yet. So what is the current state of affairs?
Could someone explain me the voting mechanism mentioned in the
document? I get that it works from left to right and com
