This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-29
Channels
- # announcements (15)
- # babashka (17)
- # beginners (66)
- # calva (18)
- # clojure (20)
- # clojure-dev (2)
- # clojure-europe (27)
- # clojure-nl (1)
- # clojure-norway (24)
- # clojure-sweden (5)
- # clojure-uk (4)
- # clr (1)
- # cursive (3)
- # datomic (10)
- # dev-tooling (9)
- # gratitude (1)
- # honeysql (5)
- # hyperfiddle (13)
- # malli (4)
- # music (1)
- # nrepl (1)
- # off-topic (31)
- # polylith (11)
- # portal (6)
- # re-frame (3)
- # reitit (4)
- # releases (1)
- # shadow-cljs (8)
- # squint (4)
- # tools-build (26)
- # vim (1)
- # yamlscript (52)
Hello! I have struggled to understand how to implement a multi-arity protocol method with a record, so I’d like to suggest an improvement to the https://github.com/clojure/clojure/blob/3eab1a5a5b4cfed86c1d0c9c21bd1892e1fb44fd/src/clj/clojure/core_deftype.clj#L344-L348 to make this clearer. Do I understand correctly that the right process is to create a Jira issue and attach a patch? (I’ve already signed the contrib. agreement). I am thinking about this change (new in cursive): > (methodname [args*] body) > > The argument and return types can be hinted on the arg and > methodname symbols. If not supplied, they will be inferred, so type > hints should be reserved for disambiguation. > > For multi-arity methods, add a separate (methodname ...) entry > for each one.
the best first step is an Ask at http://ask.clojure.org and then if it isn't immediately dismissed, alex or jared will create a jira ticket