-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
Move Object
internal object methods to GcObject
#835
Conversation
Codecov Report
@@ Coverage Diff @@
## master #835 +/- ##
==========================================
- Coverage 59.30% 59.29% -0.02%
==========================================
Files 165 165
Lines 10342 10376 +34
==========================================
+ Hits 6133 6152 +19
- Misses 4209 4224 +15
Continue to review full report at Codecov.
|
Benchmark for 44ad89aClick to view benchmark
|
Looking at the benchmarks there isn't that big of a regression, as I expected. |
I'm guessing many times the compiler can statically remove some checks. |
fd16259
to
5109d83
Compare
Benchmark for a4e0864Click to view benchmark
|
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.
Other than updating the comments and the lifetime naming it looks fine.
Benchmark for 35865cfClick to view benchmark
|
cb5d69f
to
25fe301
Compare
Benchmark for 55881f0Click to view benchmark
|
Why move the methods?
Moving Object internal methods to
GcObject
because we borrow the object and we hold on to it and if an accessor (getters/setters) was to access the object it will give a borrow panic.I expect some performance regression, since we do more borrow checks.