This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-20
Channels
- # architecture (25)
- # beginners (68)
- # cider (10)
- # clara (3)
- # cljs-dev (90)
- # cljsrn (16)
- # clojure (132)
- # clojure-austin (7)
- # clojure-berlin (3)
- # clojure-czech (1)
- # clojure-dusseldorf (1)
- # clojure-greece (5)
- # clojure-italy (39)
- # clojure-spec (5)
- # clojure-uk (78)
- # clojured (2)
- # clojurescript (92)
- # community-development (6)
- # cursive (7)
- # data-science (1)
- # datascript (14)
- # datomic (32)
- # duct (8)
- # emacs (5)
- # figwheel (3)
- # fulcro (47)
- # hoplon (12)
- # jobs (10)
- # luminus (16)
- # lumo (5)
- # off-topic (1)
- # onyx (2)
- # parinfer (47)
- # pedestal (6)
- # re-frame (10)
- # reagent (2)
- # reitit (61)
- # ring (8)
- # ring-swagger (16)
- # shadow-cljs (116)
- # sql (17)
- # utah-clojurians (2)
- # vim (1)
The copying trick here: http://mrale.ph/blog/2018/02/03/maybe-you-dont-need-rust-to-speed-up-your-js.html
@rauh there is a rust version of datascript https://github.com/mozilla/mentat
cooool
i think that's exactly what i need for something
Given (defonce !conn (d/create-conn))`, a call to (set! !conn (d/conn-from-datoms (d/datoms @!conn :eavt)) db-schema)
throws Figwheel Compile Exception: set! target must be a field or a symbol naming a var
Well spotted @rauh. What will help me find errors like that? It's super common
Honestly, parinfer has helped me massively with this. Of course, if you write everything on one line, it's no win. But it ends up encouraging you to break things down a certain way so that these mistakes happen less often because it forces the ast/paren structure to match the indentation, so that you have certain visual guarantees about what's getting passed where.
This made me think of a rainbow parens feature that would help a lot: instead of just coloring the parens yellow/green/purple, it should also color the symbols inside the rainbow parens because they matter the most. So if there was a toggle (hold down some key) or a permanent underline where the symbols are also rainbow-colored, this error would have popped right out.
e.g. (PURPLE purple-arg1 (YELLOW yellow arg1) bad-purple-arg2)
you'd immediately see that bad-purple-arg2
belongs under YELLOW.
That's not a bad idea!
parinfer ftw, just break everything onto a new line
This made me think of a rainbow parens feature that would help a lot: instead of just coloring the parens yellow/green/purple, it should also color the symbols inside the rainbow parens because they matter the most. So if there was a toggle (hold down some key) or a permanent underline where the symbols are also rainbow-colored, this error would have popped right out.
e.g. (PURPLE purple-arg1 (YELLOW yellow arg1) bad-purple-arg2)
you'd immediately see that bad-purple-arg2
belongs under YELLOW.