{"push_id":695980811,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"fb8d1c8f504163d1ada8a2a98df24b36cec9f2b6","before":"350b67410cc2f58f79e010b251d7c9229668a553","commits":[{"sha":"9042beef7c80b3936eb525dca8b210642a7f5201","author":{"email":"34e6c836575097c76965abe8873967ccff230386@gmail.com","name":"Eric Christopher"},"message":"Remove duplicate conditional in if-stmt.\n\nFixes PR23839.","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project-submodule/commits/9042beef7c80b3936eb525dca8b210642a7f5201"},{"sha":"fb8d1c8f504163d1ada8a2a98df24b36cec9f2b6","author":{"email":"145cd9ce43438a13beb2c4f51a87276bf83881e7@apple.com","name":"Greg Clayton"},"message":"Found an issue that was causing types to be completed much more often than they needed to be.\n\nThe problem is for lldb_private::Type instances that have encoding types (pointer/reference/const/volatile/restrict/typedef to type with user ID 0x123). If they started out with m_flags.clang_type_resolve_state being set to eResolveStateUnresolved (0), then when we would call Type::ResolveClangType(eResolveStateForward) we would complete the full type due to logic errors in the code.\n\nWe now only complete the type if clang_type_resolve_state is eResolveStateLayout or eResolveStateFull and we correctly upgrade the type's current completion state to eResolveStateForward after we make a forward delcaration to the pointer/reference/const/volatile/restrict/typedef type instead of leaving it set to eResolveStateUnresolved.","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project-submodule/commits/fb8d1c8f504163d1ada8a2a98df24b36cec9f2b6"}]}