Fork me on GitHub
#parinfer
<
2018-02-13
>
cfleming00:02:44

(there are some more replies to that part below)

shaunlebron00:02:04

ah, indenting docstrings!

shaunlebron00:02:11

i’ll think about it

shaunlebron00:02:46

yeah, I don’t like multiline strings in clojure

shaunlebron00:02:45

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

shaunlebron00:02:04

it would be fine with docstrings

shaunlebron00:02:15

but there could be strings where that is not okay

cfleming00:02:35

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

cfleming00:02:44

Right, definitely.

shaunlebron00:02:56

yeah, that ship has sailed for clojure

cfleming00:02:21

Indeed, sadly.

shaunlebron00:02:22

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

cfleming00:02:47

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

cfleming00:02:04

But even there indentation is significant.

shaunlebron00:02:53

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

cfleming00:02:04

Great, thanks!

shaunlebron00:02:14

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

shaunlebron00:02:22

i star too many repos

cfleming00:02:27

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

shaunlebron00:02:35

i couldn’t find a syntax guide for it

shaunlebron00:02:49

yeah, I thought it was carp, not sure though

cfleming00:02:22

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.

shaunlebron00:02:32

it might be Hy

cfleming00:02:38

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

shaunlebron00:02:51

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

cfleming00:02:17

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

cfleming00:02:32

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

tianshu03:02:14

@shaunlebron is that transformChange will never return undefined?

shaunlebron03:02:27

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

shaunlebron03:02:35

just guarding against bad plugin integration

tianshu03:02:52

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

tianshu03:02:37

maybe I should port from parinfer-jvm?

tianshu03:02:07

it's likely very old

shaunlebron03:02:16

parinfer-jvm will be updated soon I think

shaunlebron03:02:41

you will be the third person this week who needs it