This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-05
Channels
- # aleph (1)
- # announcements (18)
- # babashka (145)
- # beginners (70)
- # calva (34)
- # cider (3)
- # clj-kondo (98)
- # cljdoc (5)
- # cljs-dev (13)
- # clojure (134)
- # clojure-europe (57)
- # clojure-nl (4)
- # clojure-uk (4)
- # clojurescript (40)
- # code-reviews (3)
- # conjure (1)
- # core-async (5)
- # data-science (3)
- # datomic (8)
- # fulcro (9)
- # google-cloud (2)
- # inf-clojure (9)
- # jobs (1)
- # lsp (9)
- # malli (25)
- # polylith (4)
- # reitit (4)
- # releases (2)
- # remote-jobs (3)
- # rewrite-clj (8)
- # shadow-cljs (34)
- # tools-build (1)
- # tools-deps (67)
@lilactown you could also do via default
if performance is not really much of a concern for your own protocols
@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
@lilactown no, those have to rely on satisfies?