This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-07
Channels
- # alda (7)
- # beginners (4)
- # boot (108)
- # cljsrn (40)
- # clojure (24)
- # clojure-berlin (1)
- # clojure-dev (20)
- # clojure-russia (21)
- # clojurescript (115)
- # clojurescript-ios (1)
- # cursive (8)
- # data-science (5)
- # datascript (3)
- # hoplon (313)
- # jobs (1)
- # ldnclj (2)
- # off-topic (19)
- # om (115)
- # portland-or (3)
- # re-frame (9)
- # yada (2)
hi @cfleming: is it intended that when you type the name of a protocol e.g. TestProtocol and let cursive do an auto-fix on the unresolved symbol that it generates
(:import (some.namespace TestProtocol))
instead of
(:require [some.namespace TestProtocol])
@snowell: it’s called “talking to the duck” http://www.rubberduckdebugging.com
@cfleming: ha - when I worked for SpringSource (actually before they became SpringSource and were still called interface21) we discussed building a ‘consultant in a box’ which eventually turned into the Eclipse Tooling. Thanks for bringing back that nightmare .
actually - that does remind me pleasantly of the inbuilt code inspections that IntelliJ offers - they do know how to do tooling, at least on the surface. Maybe Colin could talk about what it’s like behind the scenes….