{"push_id":2643699953,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"fbf3dac5db6695b28a5ef0b3b81d9d176f660806","before":"e0e4abe182451cbea5e24b898aa654130bb4d81f","commits":[{"sha":"fbf3dac5db6695b28a5ef0b3b81d9d176f660806","author":{"name":"Artem Dergachev","email":"6cbf4556c0fbd074258a67000a54f5a83515d78c@gmail.com"},"message":"[analyzer] Re-enable C++17-specific RVO construction contexts.\n\nNot contexts themselves, but rather support for them in the analyzer.\n\nSuch construction contexts appear when C++17 mandatory copy elision occurs\nwhile returning an object from a function, and presence of a destructor causes\na CXXBindTemporaryExpr to appear in the AST.\n\nAdditionally, such construction contexts may be chained, because a return-value\nconstruction context doesn't really explain where the object is being returned\ninto, but only points to the parent stack frame, where the object may be\nconsumed by literally anything including another return statement. This\nbehavior is now modeled correctly by the analyzer as long as the object is not\nreturned beyond the boundaries of the analysis.\n\nDifferential Revision: https://reviews.llvm.org/D47405","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project-20170507/commits/fbf3dac5db6695b28a5ef0b3b81d9d176f660806"}]}
{"actor":{"display_login":"chapuni"}}