Hi Bijan


> Because the use of #as: methods is slightly harder and more
> counterintuitive than #asFoo methods? Part of this might just be not being
> used to it, but there's definitely the precedence issue.
> 
> Actually, I tend to prefer a little pollution of classes to horkiness in
> my statements.
> 
> I suspect that that's why lots of folks prefer #filestream type methods to
> Filestream class>>on:, etc.
> 
> Perhaps the right, if slow, solution is to generalize the mechanism so
> that #asFoo expands/is DNU trapped to Foo fromReceiverType: receiver.

NO NO NO.

This is not we have DNU that we should use it for basic engineering
problems. DNU is a meta approach that will hamper code analysis and make
things to complex.

This is also why this is cool to use changeClass but why we should not using
while implementing state pattern.


> Cheers,
> Bijan Parsia.
> 
>