{"push_id":730494275,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"f5a7bba986d82e0dfc5fd7bce2b8ed78a5b970b5","before":"54add5ac9ae0b6abb11f4a5ccbac1b1ca38a4e27","commits":[{"sha":"812703139c5c1836a97456eb9a0b84f49b8cc850","author":{"email":"d659c10e27d52b00987b65e85d99bce5480adcae@cryptonector.com","name":"Nicolas Williams"},"message":"Use =, not ==, for shell tests","distinct":true,"url":"https://api.github.com/repos/dtolnay/jq/commits/812703139c5c1836a97456eb9a0b84f49b8cc850"},{"sha":"1628bbf95f8a58424dd3928692fcbf0f307272ec","author":{"email":"1480464b87745a0822a0e8b7545ca981d8e7352e@gmail.com","name":"David Tolnay"},"message":"Clean up trailing whitespace","distinct":true,"url":"https://api.github.com/repos/dtolnay/jq/commits/1628bbf95f8a58424dd3928692fcbf0f307272ec"},{"sha":"66ef8e2c243207bb4edd88c409ce90fc95e0dffe","author":{"email":"1480464b87745a0822a0e8b7545ca981d8e7352e@gmail.com","name":"David Tolnay"},"message":"Resolve shift/reduce conflict of 'def' vs '|'\n\nThis was an important conflict. In the following expression:\n\n    def a: 0; . | a\n\nBison needs to decide between these two equally valid\nparses:\n\n    (def a: 0; .) | a\n    def a: 0; (. | a)\n\nFor jq we want the second one, because the first results in\n\"a/0 is not defined\". In the current parser the first parse\nis a reduce and the second parse is a shift. Since Bison\nprefers to shift in shift/reduce conflicts, we accidentally\ngot the correct behavior.\n\nThis commit adds a precedence level FUNCDEF which is lower\nprecedence than '|', meaning we explicitly choose the\ncorrect parse.\n\nOf course many unit tests already cover this case, but I\nadded one specifically for it.","distinct":true,"url":"https://api.github.com/repos/dtolnay/jq/commits/66ef8e2c243207bb4edd88c409ce90fc95e0dffe"},{"sha":"f5a7bba986d82e0dfc5fd7bce2b8ed78a5b970b5","author":{"email":"1480464b87745a0822a0e8b7545ca981d8e7352e@gmail.com","name":"David Tolnay"},"message":"Resolve remaining shift/reduce conflicts involving '?'\n\nBy lowering the precedence of rules that should never use\nthe generic Exp '?' rule.","distinct":true,"url":"https://api.github.com/repos/dtolnay/jq/commits/f5a7bba986d82e0dfc5fd7bce2b8ed78a5b970b5"}]}