better solution for finding the start of "parent expressions"

[oakmac]

Right now we are assuming that an open paren as the first character of a line is the start of a new expression. There are circumstances where this is not true (example: multi-line strings) and will cause odd behavior from the main Parinfer algorithm.

Need to find a better solution here.

[jasongilman]

I'm the maintainer of Proto REPL. I had a similar issue and found that using Atom can tell you the context for any code by using scopes. See https://github.com/jasongilman/proto-repl/blob/master/lib/editor-utils.coffee#L45

[oakmac]

Awesome! Thank you for posting this.

[oakmac]

sublime-text-parinfer has some interesting discussion on the "parent expression hack"