This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-07
Channels
- # aleph (19)
- # aws (1)
- # beginners (75)
- # boot (28)
- # cider (1)
- # cljs-dev (12)
- # cljsrn (20)
- # clojure (350)
- # clojure-argentina (1)
- # clojure-chicago (2)
- # clojure-dev (2)
- # clojure-russia (5)
- # clojure-spec (2)
- # clojure-uk (14)
- # clojure-ukraine (3)
- # clojurescript (68)
- # component (87)
- # core-async (25)
- # core-logic (13)
- # cursive (4)
- # data-science (72)
- # datascript (59)
- # datomic (15)
- # defnpodcast (7)
- # emacs (33)
- # hoplon (5)
- # immutant (73)
- # jobs (21)
- # klipse (6)
- # lumo (14)
- # off-topic (26)
- # om (23)
- # onyx (6)
- # parinfer (37)
- # protorepl (4)
- # re-frame (13)
- # ring (2)
- # rum (3)
- # spacemacs (2)
- # specter (22)
- # sql (47)
- # uncomplicate (10)
- # unrepl (79)
- # untangled (66)
- # vim (47)
- # yada (17)
I made a major change to Parinfer last year and called it v2
the change was related to how to handle an unmatched close-paren
Chris thinks it was a mistake, and we’re having a minor debate about it here: https://github.com/oakmac/atom-parinfer/issues/76
i’d like to hear your opinion though @cfleming @sekao @bhurlow @doglooksgood (or others)
for now, leaving imbalanced state. I have to type close parens manually. before V2, I do the same. is there I missed something?
maybe that's not something parinfer should be doing, maybe you should complement parinfer with an auto-close plugin
thanks guys, i’ll work on an implementation so we can see how it feels
@doglooksgood you have to type close-parens manually for both v1 and v2 in the case described. the new rules may prevent that
wrote up a summary of the new proposal: https://github.com/shaunlebron/parinfer/issues/131
also, going to build a formatter to help use parinfer on teams: https://github.com/shaunlebron/parinfer/issues/132
@dominicm will do
I have noticed that zprint is quite slow against whole files from lumo. So maybe I should take back that idea 😛
prettier runs pretty fast, I’ll be looking how they do it
zprint?
prettier is based on a paper: http://homepages.inf.ed.ac.uk/wadler/papers/prettier/prettier.pdf no idea if the speed comes from this
oh, i thought we were talking about node’s i/o
parinfer on node is lightning fast though
15ms per 3k lines?
can’t remember, but it’s fine
zprint is clojurescript (on lumo). So that might be it. But it was definitely a big pause for a single file. Like ~30s or so.
oh wow, I didn’t know about this, only heard of cljfmt
I've no idea why nvim parinfer doesn't feel fast on my machine then, it's a new laptop. Maybe something misconfigured, or it's using the clojure one still
maybe my benchmarks are off, atom-parinfer always felt fast to me, but it does limit itself to the parent expression
we’ll see, I’ll tag you for feedback when it’s ready
any ideas for the name of the cli command? @dominicm
I’d probably settle for parinfer-fmt if we’re going that direction
or parinfer-prettify or just parinfer