@lilactown you could also do via default if performance is not really much of a concern for your own protocols

i.e. default + satisifes? etc.

yeah, I was originally trying to get around checking satisfies? for perf

@lilactown there's really no way to do what you want and for it to be fast

is satisfies that slow? I ask because satisfies checks are a good chunk of what our app does when handling http responses and it hasn’t been that big a deal

@emccue it's not that slow, generally when I'm saying "slow" I mean something that might appear in an inner loop and thus not be suitable

what i ended up doing is what emccue suggested above: adding checks for classes of types like sequential? map? set? and then falling back to protocol dispatch

i'm assuming that sequential? et al. are faster than satisfies?

haven't benchmarked it yet

@lilactown no, those have to rely on satisfies?

ah

the map? one might be an issue since most custom types could be records now that i think about it

So you probably actually want

(defn method [o]
  (cond
    (satisfies? Proto o) 
    (method* o)

    (map? o)
    (map-impl o)

    (set? o)
    (set-impl o)

    (sequential? o)
    (sequential-impl o)

    :else
    (throw (ex-info "" {})))