parinfer 2018-02-13

(there are some more replies to that part below)

ah, indenting docstrings!

i’ll think about it

yeah, I don’t like multiline strings in clojure

we have to preserve structure in front of a change, so we can’t shift multiline string indentation without breaking strings

it would be fine with docstrings

but there could be strings where that is not okay

Yeah, and the fact that the docstrings are not HTML or similar makes them a real pain to indent when displaying them.

Right, definitely.

yeah, that ship has sailed for clojure

Indeed, sadly.

i’ve seen new clojure-based lisps where they make indentation significant in multiline strings, seems to be a common pain point

That said, there are projects using markdown in their docstrings now, I’m planning to add an option to Cursive to display that.

But even there indentation is significant.

@cfleming: i replied in the thread, thanks for the headsup

Great, thanks!

wish I could find that Lisp that had stricter multiline string indentation

i star too many repos

Yeah, that’s a nice idea. Carp, maybe?

i couldn’t find a syntax guide for it

yeah, I thought it was carp, not sure though

There are quite a few now. Carp and Pixie are the ones that spring to mind, but I’m sure there are more. Oh and Hy.

it might be Hy

Actually, Hy is probably a top contender due to its Python heritage.

ha, I can’t spend anymore time tonight tracking this down

I can’t find anything about it in Hy documentation.

It’ll have to remain a mystery. Nice idea though.

@shaunlebron is that transformChange will never return undefined?

@doglooksgood yeah, safe to say it’ll never be undefined

just guarding against bad plugin integration

I think when porting, is very important to know immutable/mutable of variables, and what will return null;

maybe I should port from parinfer-jvm?

it's likely very old

parinfer-jvm will be updated soon I think

you will be the third person this week who needs it