[PEAK] peak.security weirdness

[Simon Belak]

First of all a great big thanks for your most informative explanation!

However I still can't help myself not to question why add the implicit 
rule for self. Is there any other reason besides automatic 
specialisation when mixing functions and methods as specialisations of a 
single generic function? Granted, it can be convenient, but it is also a 
bit "magical", isn't it?
What's even worse, doesn't this reduce usability? If I understand 
correctly, one of the reasons why Python uses explicit self is to enable 
instances to "borrow" methods from other classes (when conforming to a 
given protocol). Implicit specialisation makes it impossible to use 
generic functions in such a context.

And now for something completely different. Is my understanding of 
evaluation order now correct? All non-parameter symbols are evaluated 
immediately while expressions are evaluated at each dispatch?
How about tautologies, are they by any chance discarded?

Cheers,
Simon