Re: RFC: Extending method specializers

Ken Tilton <kennytilton@xxxxxxxxxxxxx> writes:

You might have the wrong question. Mine would be why you would want
generic dispatch to do such a thing. My answer would be that you have
fallen in love with the mechanism, and now want to use it for
everything in sight.
The very experience of learning CLOS quickly results in unrealistic
expectations. People learn the basics, start using CLOS for practical
things, and eventually run into a situation where they want to do
something special. They search a little, and find to their delight
that they can extend/customize CLOS with fairly little effort to do
exactly what they want. Rinse and repeat, a number of times.

Sooner or later they run into an aspect of CLOS that cannot be easily
customized (of course this happens later rather than sooner because
MOP addresses most things people want to do). At that point the idea
that CLOS cannot be bent to the will of the programmer is impossible
to swallow. So people try to put square pegs through round holes (and
often succeed).

Once you let us customize class composition and discriminating
functions, can you really blame us for wanting ML-style pattern
matching in method specializers? :)

--
Regards,
Slava Akhmechet.
.