-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial pass of removing scoped_ptr/scoped_array #1163
Conversation
3445026
to
91785b3
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1163 +/- ##
==========================================
+ Coverage 56.52% 56.53% +0.01%
==========================================
Files 1899 1899
Lines 94249 94307 +58
==========================================
+ Hits 53270 53317 +47
- Misses 40979 40990 +11 ☔ View full report in Codecov by Sentry. |
e4faf01
to
08c62bc
Compare
08c62bc
to
65fe06f
Compare
Note this is a draft, depends on youtube#1163 b/291356560
eee2561
to
8ae4601
Compare
Switches to use unique_ptr instead of scoped_ptr where possible and it doens't break tests. The intent is to remove starboard/common/scoped_ptr fully. b/291356560
8ae4601
to
f57c2c0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but can you tell me if the current test failures are legitimate?
For internal builds they are yes. Haven't had time to debug - i've been backing changes out one by one. External builds are ( were ? ) fine, except that the lab has been down for couple days for on-device tests. |
OK LMK when tests are passing. |
This is now worked on in #2427 Conveerting to a draft |
Switches to use unique_ptr instead of scoped_ptr where possible and it doesn't break tests.
The intent is to remove starboard/common/scoped_ptr fully.
b/291356560