{"push_id":1376810650,"size":1,"distinct_size":1,"ref":"refs/heads/decaffeinate-fork-1.10.0","head":"e6fb86340f6e06a0f7ec454ed818652ebe5cb024","before":"2a1fe8a3a8234cc40f26b838264bcfbdaf3a292f","commits":[{"sha":"e6fb86340f6e06a0f7ec454ed818652ebe5cb024","author":{"name":"Alan Pierce","email":"d34ec7139604a3b9d8ba8ff59e142f00e8205dd9@gmail.com"},"message":"fix: also include generated } tokens when fixing closing token positions (#10)\n\nCloses https://github.com/decaffeinate/decaffeinate/issues/458\r\nCloses https://github.com/decaffeinate/decaffeinate/issues/461\r\nCloses https://github.com/decaffeinate/decaffeinate/issues/504\r\n\r\nJust like OUTDENT and CALL_END tokens, close-curly-brace tokens can be generated\r\nwithout having a real location, and if that position overlaps with a later\r\ntoken, it can cause the AST to have bad location data. Just like the other two\r\ntoken types, we now give `}` tokens the position of the previous real token,\r\nwhich makes all AST nodes have reasonable locations.","distinct":true,"url":"https://api.github.com/repos/decaffeinate/coffeescript/commits/e6fb86340f6e06a0f7ec454ed818652ebe5cb024"}]}
{"actor":{"display_login":"alangpierce"}}