Akim Demaille
Akim Demaille
Hi Markus, I think I face the same issue again, under a different disguise. ```ruby require 'parser/current' require 'unparser' ast = Unparser.parse(
Hi, I would go for option 2. Have a look at https://www.gnu.org/software/bison/manual/html_node/Syntax-Error-Reporting-Function.html. This should provide you with all you need to filter out the disabled tokens. Cheers!
Ping. This is really a problem when migrating to newer versions of Ruby, 3.1 included.
It's a pity that this project is stuck. Is there a more lively fork somewhere?
Thanks!
Please, tag this release. We have whole CIs jammed because of this. Thanks in advance!
(Also, FWIW, using `
Also, the doc pointed to, https://whitequark.github.io/parser/, is completely outdated. Maybe it could be updated automatically using GitHub actions?
Likewise. FWIW, this statement is not very convincing to me: > If `@foo&.bar? && @foo.baz?` ever becomes `@foo.baz?` then nil safety is lost. It is up to the developer to...
This is fine by me. @Earlopain 's suggestion for fetch is nice, we will probably move to it. Thanks to both of you.