refactor: use raw_ref in RootView #42114
Merged
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.
Description of Change
Make the ownership / nullability contract for
RootView
fields a little stricter:raw_ref<T>
instead ofraw_ptr<T>
for class fields that can never benullptr
ViewTracker
directly since RootView already owns it, and its lifecycle is identical to the RootView, and the RootView header was already including the ViewTracker headerAll reviews welcomed. CC @nornagon as most recent committer and @miniak for general C++ tidying 馃樃
Checklist
npm test
passesRelease Notes
Notes: none.