Markus Schirp
Markus Schirp
This is a public build showing the issue, this is with `stack --verbose`. Not showing the full CLI. I suspect its the github actions environment leading to longer paths. https://github.com/mbj/stack-deploy/runs/1445686795?check_suite_focus=true#step:6:11422
For anyone watching here the issue is the number of modules running into OSX specific limits on the command line size. The trick will be to split up this project...
2 issues play in here: First: There are dynamic strings that produce AST that can *only* be the result of parsing heredocs. And the signature for these ASTs of "must...
@akimd its my end goal that unparser can round trip *ALL* ast that parser emits. Which may mean I'll have to ask the parser team to simplfy the ast. I'm...
@akimd I recently spend a bit more time to think about the problem. Overall I've to conclude that the current `parser` AST, on any form of dynamic strings is currently...
> Oh, you have a new face :) ageless version ;) > Unparser is the final part of a parse|transform|unparse pipe. We don't care about exact syntactic round tripping, we...
@akimd `Unparser.parse` "is" the parsers parser, but it uses the [modernized](https://github.com/whitequark/parser#usage) AST format. Thats all I want to know.
So are you using the modernized AST Format or not?
kk, so as a recomemndation: The parsers default AST format is lossy on semantics, and unparser only supports the modern one for that reason. Also all other major users of...
Also a fix for this issue will probably only ever land in the modern AST format.