[Clang][NFC][Coroutine] Do not leave dangling pointers after removing CoroBegin #98546
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In
handleNoSuspendCoroutine
we delete the coro.begin intrinsic in lieu of splitting. After this operationShape.CoroBegin
becomes dangling. A new patch I am working on needs to tell that this happened.After setting the dangling pointer to nullptr, I found that the only usage for the dangling pointer in the code is
updateCallGraphAfterCoroutineSplit
. After some investigation, the logic that checksCoroBegin
's existence is not very useful. You would still need to removeCoroEnd
s and do the necessary updates regardless.