-
Notifications
You must be signed in to change notification settings - Fork 36
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
Optimize interning #53
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #53 +/- ##
=======================================
+ Coverage 52.3% 54.7% +2.4%
=======================================
Files 38 38
Lines 4967 5339 +372
=======================================
+ Hits 2598 2923 +325
- Misses 2369 2416 +47 ☔ View full report in Codecov by Sentry. |
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.
Just a suggestion I'd recommend include a benchmark to demostrate the performance improvement
@TommyCpp I introduced benchmark in separate pull request |
Setup: Output of
Results of
Results of
|
@Hartigan could you resolve the CI failures? |
@cijothomas Looks like it's broken in
|
Oops! Sorry, looks like main is broken #57 (comment) |
pub(crate) struct StringInterner { | ||
data: IndexSet<String>, | ||
#[cfg(any( | ||
feature = "intern-ahash", |
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.
nit: A OR (A AND B)
Let's reduce complexity here.
tests in
|
@cijothomas these tests are unaltered to this PR i don't see a blocker here. |
Yes I didn't mean to block this PR! But is main itself broken? |
@cijothomas I think, |
@Hartigan Seems this was somehow missed, and is still good to go. Can you please resolve the conflicts? |
@mstyura Can you fix the lint issues that is causing CI to red? |
@cijothomas could you please approve new CI run? |
CI failure is now unrelated to code itself and fails due to rate limiting of GitHub API:
|
Trying to reduce allocations and copies