Conversation

This Tweet was deleted by the Tweet author. Learn more
Tangentially related, but I wonder what's the right way to do things when the language has some amount of whitespace sensitivity. Like indentation, or spaces required around binops, or newlines terminate statements (but are also allowed in the middle of expressions)...
1
2
The last time I tried that, having a separate tokenizer and parser but the former having a "newline" token for the last bit above, the latter ended up very hacky.
1
3
What I do in Kitten is have a lexing pass that generates tokens annotated with source spans, followed by a bracketing pass that desugars them into explicitly delimited blocks using those spansโ€”the concept of an โ€œindent/dedent tokenโ€ seems obvious but doesnโ€™t work well in practice
1
5
(Because youโ€™re attempting to deduce the bracketing as if it were already present, in addition to the basic mistakes of mixing concerns)
1
2
Hmm. I mentioned the other things just to avoid being overly specific, but my overly specific problem was with the "newlines terminate statements (but are also allowed elsewhere)" thing -- does your advice translate to that case?
1
Yeahโ€”the specifics depend on what you want to do in particular, but for example I allow newlines within parentheses/square braces, or outside a layout context, and they donโ€™t cause statement terminators to be inserted there
1
2
I've been doing some work in fsharp recently and .. whoo boy I did not expect to have so many feelings against whitespace sensitivity boil up all of a sudden. But for real: it does not go well in expression languages where you're doing a lot of nesting & continuation lines.
1
6
It's weird because it did not bother me in haskell (nor python) but it's like fingernails on blackboard in fsharp. Might just be the years I've spent doing ocaml which is not. But also I think there's much more rightward drift with pervasive keyword args and module decl nesting.
3
2
Show replies