-
Notifications
You must be signed in to change notification settings - Fork 5
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
Use SVector in all trace methods #207
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #207 +/- ##
==========================================
- Coverage 84.46% 84.27% -0.19%
==========================================
Files 9 9
Lines 695 687 -8
==========================================
- Hits 587 579 -8
Misses 108 108 ☔ View full report in Codecov by Sentry. |
Benchmark Results
|
BTW |
Based on my test, the time difference is almost negligible. |
Check if the usage of
SVector
is helpful in all cases.