{"push_id":2526375071,"size":1,"distinct_size":1,"ref":"refs/heads/trunk","head":"4118e77621954fec9cf427f57ad4363f6f9b521e","before":"1f0532ab2d2acf0d08745c5795af8c9039ac43b5","commits":[{"sha":"4118e77621954fec9cf427f57ad4363f6f9b521e","author":{"name":"rsmith","email":"63b43c65837b5b2140b45f7f0c3e417ac60f5cc0@91177308-0d34-0410-b5e6-96231b3b80d8"},"message":"PR37189 Fix incorrect end source location and spelling for a split '>>' token.\n\nWhen a '>>' token is split into two '>' tokens (in C++11 onwards), or (as an\nextension) when we do the same for other tokens starting with a '>', we can't\njust use a location pointing to the first '>' as the location of the split\ntoken, because that would result in our miscomputing the length and spelling\nfor the token. As a consequence, for example, a refactoring replacing 'A<X>'\nwith something else would sometimes replace one character too many, and\nsimilarly diagnostics highlighting a template-id source range would highlight\none character too many.\n\nFix this by creating an expansion range covering the first character of the\n'>>' token, whose spelling is '>'. For this to work, we generalize the\nexpansion range of a macro FileID to be either a token range (the common case)\nor a character range (used in this new case).\n\n\ngit-svn-id: http://llvm.org/svn/llvm-project/cfe/trunk@331155 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/spurious/clang-mirror/commits/4118e77621954fec9cf427f57ad4363f6f9b521e"}]}
{"actor":{"display_login":"spurious"}}