Um, this is all going down a path that I don't propose to follow. I am
manifestly aware that there are loads of alternatives already in Clojure
(and Java, for that matter), and many reasons both theoretical and practical
for doing or not doing all manner of things. But, a couple of remarks:
@Al
"Marker interface" is the right idea (and I did in fact look it up in
Wikipedia last night :-)), but I was trying to avoid saying that. What my
stuff is doing is arguably a little different: a Java analogy would be
something like defining a new interface that's a composite of several other
inte
Somehow, I just knew someone was going ask "why...?" :-)
A while back, I constructed a little mechanism for defining data types,
built on top of the protocol/record/type mechanism. Under certain
circumstances, it generates protocols with no methods, basically in
situations where it wants to ide
I finally got around to trying out the 1.3 release yesterday with a batch of
code that was constructed using 1.2, and promptly ran into a problem. In
1.2, it's possible to define a protocol with zero methods, so, for example,
(defprotocol
xxx) works just fine. In 1.3, this generates the rather
