This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-03-29
Channels
- # announcements (1)
- # biff (5)
- # calva (10)
- # cljdoc (4)
- # clojure (17)
- # clojure-europe (15)
- # clojure-norway (38)
- # clojurescript (53)
- # community-development (1)
- # cursive (2)
- # datomic (14)
- # fulcro (11)
- # funcool (1)
- # hyperfiddle (7)
- # introduce-yourself (2)
- # jobs-discuss (17)
- # missionary (7)
- # releases (4)
- # shadow-cljs (30)
- # slack-help (6)
- # specter (5)
- # squint (22)
In a lot of cases where Clojure compiler will use reflection Cursive seems to know which method instance will be used. So this means I get no warning that method call is ambigous. Example:
(.setScale n digits RoundingMode/HALF_UP)
Cursive seems to understand this is a call of specific method in BigDecimal class. But clojure compiler, if warn on reflection is on, will issue a warning:
call to method setScale can't be resolved (target class is unknown).
Interestingly enough, if I typehint the receiver I get warning in Cursive too:👀 1