1. 18 8月, 2015 1 次提交
  2. 16 8月, 2015 7 次提交
  3. 14 8月, 2015 3 次提交
  4. 12 8月, 2015 1 次提交
  5. 05 8月, 2015 1 次提交
  6. 28 7月, 2015 2 次提交
  7. 27 7月, 2015 3 次提交
  8. 26 7月, 2015 3 次提交
  9. 25 7月, 2015 7 次提交
  10. 24 7月, 2015 3 次提交
  11. 20 7月, 2015 3 次提交
    • D
      Resolve remaining shift/reduce conflicts involving '?' · f5a7bba9
      David Tolnay 提交于
      By lowering the precedence of rules that should never use
      the generic Exp '?' rule.
      f5a7bba9
    • D
      Resolve shift/reduce conflict of 'def' vs '|' · 66ef8e2c
      David Tolnay 提交于
      This was an important conflict. In the following expression:
      
          def a: 0; . | a
      
      Bison needs to decide between these two equally valid
      parses:
      
          (def a: 0; .) | a
          def a: 0; (. | a)
      
      For jq we want the second one, because the first results in
      "a/0 is not defined". In the current parser the first parse
      is a reduce and the second parse is a shift. Since Bison
      prefers to shift in shift/reduce conflicts, we accidentally
      got the correct behavior.
      
      This commit adds a precedence level FUNCDEF which is lower
      precedence than '|', meaning we explicitly choose the
      correct parse.
      
      Of course many unit tests already cover this case, but I
      added one specifically for it.
      66ef8e2c
    • D
      Clean up trailing whitespace · 1628bbf9
      David Tolnay 提交于
      1628bbf9
  12. 19 7月, 2015 1 次提交
  13. 11 7月, 2015 5 次提交