This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-02
Channels
- # beginners (26)
- # bitcoin (1)
- # boot (9)
- # boot-dev (5)
- # cider (26)
- # cljs-dev (1)
- # clojure (190)
- # clojure-finland (1)
- # clojure-italy (42)
- # clojure-nl (20)
- # clojure-russia (3)
- # clojure-sanfrancisco (1)
- # clojure-serbia (1)
- # clojure-spec (50)
- # clojure-uk (16)
- # clojurescript (62)
- # core-async (4)
- # cryogen (1)
- # cursive (6)
- # datascript (1)
- # datomic (36)
- # duct (6)
- # editors (6)
- # emacs (14)
- # graphql (3)
- # leiningen (30)
- # off-topic (21)
- # om (7)
- # parinfer (13)
- # portkey (56)
- # re-frame (2)
- # reagent (2)
- # shadow-cljs (58)
- # vim (1)
- # yada (3)
@doglooksgood is there a need for it still? are you using parinfer-rust?
can you elaborate on this
@shaunlebron @doglooksgood FWIW I’m finding the edits a source of hard-to-fix bugs. I’m planning to move to a model which returns changed lines instead of all the individual edits. This should be easier since parinfer is quite line-based.
@eraserhd you’re mixing up input changes with output changes I think
input changes need to be exact to infer the right output changes
unless the output changes themselves become detected as input changes
@eraserhd Right, Cursive’s implementation doesn’t split the input into lines, and instead of returning another whole document returns just the edits to the original document. This greatly reduces GC pressure and is much more efficient (in IntelliJ, at least, and I’m pretty sure most editors)