|
From: | Domingo Alvarez Duarte |
Subject: | About how reduce/reduce conflicts are managed |
Date: | Sun, 19 Nov 2023 10:57:26 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 |
Hello !While converting this grammar https://github.com/diku-dk/futhark/blob/master/src/Language/Futhark/Parser/Parser.y to be used in https://mingodad.github.io/parsertl-playground/playground/ I found that bison/byacc/kmyacc reports 35 reduce/reduce conflicts but parsertl reports then as resolved.
Then I found that https://github.com/BenHanson/parsertl14 that I'm using was using precedence to solve reduce/reduce conflicts like "lemon" and "happy" does.
Then I started asking then about that decision/issue (https://github.com/BenHanson/parsertl14/issues/15 , https://sqlite.org/forum/forumpost/79cbc282a5 , https://github.com/haskell/happy/issues/260 ) and there is doubts about how best to handle it, including questioning how bison does it.
Can someone help in clarifying this ? Cheers !
[Prev in Thread] | Current Thread | [Next in Thread] |