[CLJ-825] Protocol implementation inconsistencies Created: 08/Aug/11 Updated: 08/Aug/11
|Affects Version/s:||Release 1.2, Release 1.3|
There seems to be some inconsistencies when implementing protocols that have multi arity functions depending on how the protocol is implemented. I have attached a clj file illustrating this. The short version is that multi arity must be defined as such w/ defrecord:
(defrecord Zomg 
And as such with extend-type
I have only tested defrecord & extend-type. I am unsure how it works with deftype and extend-protocol.