This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-07
Channels
- # admin-announcements (2)
- # arachne (1)
- # bangalore-clj (2)
- # beginners (39)
- # boot (349)
- # cider (31)
- # clara (2)
- # cljs-dev (9)
- # cljsjs (67)
- # cljsrn (7)
- # clojure (300)
- # clojure-art (4)
- # clojure-greece (11)
- # clojure-hk (3)
- # clojure-israel (1)
- # clojure-italy (17)
- # clojure-japan (1)
- # clojure-russia (33)
- # clojure-sg (2)
- # clojure-spec (41)
- # clojure-uk (86)
- # clojurescript (123)
- # clojurex (3)
- # code-reviews (1)
- # component (6)
- # crypto (1)
- # cursive (36)
- # datomic (32)
- # devcards (3)
- # emacs (11)
- # events (3)
- # funcool (4)
- # luminus (10)
- # om (28)
- # onyx (88)
- # pedestal (2)
- # re-frame (84)
- # reagent (7)
- # ring-swagger (3)
- # specter (33)
- # sql (2)
- # vim (21)
@eslachance shouldn’t that be db/save-message!
in the screenshot?
I copy/pasted directly from the guide. The issue was the order of the code
Clojure uses a single pass compiler, so you do have to make sure stuff is defined in order
I've been doing a whole lot of coding with node.js with event handlers that don't require any sort of order. 🙂
I find that a nice side effect of this is that it enforces a common structure on namespaces
the top level functions are always at the bottom, and things get more specific as you go up
so whenever you’re looking through some new code, you can always scroll down and work your way up without having to jump around the file all the time to figure out what’s happening
Oh yeah it's actually fine, it's just something one needs to get used to I guess - compared to JS specifically I mean.