szos / cl-advice Goto Github PK

Hello again :)

Nothing of much importance, but I wonder about the design decision of making an explicit distinction between advisable and non-advisable functions. Why is it that you require a function to be defined or converted explicitly to advisable, and signal an error otherwise?

Let's say ensure-adivisable-function, instead of signal an error on unadvised functions, converted the function to advisable if it is not already, on the fly. Then you could just install advice on any function, regardless of if that function was declared as advisable or not, and without an explicit conversion/declaration.

Would you agree to adding this to Quicklisp?