Skip to content
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

Add remove() to bitmask_binop! #904

Merged
merged 1 commit into from
Nov 24, 2023
Merged

Add remove() to bitmask_binop! #904

merged 1 commit into from
Nov 24, 2023

Conversation

psychon
Copy link
Owner

@psychon psychon commented Nov 24, 2023

In this commit, I am adding a new function remove() to the bitmask_binop! macro. This function removes some set bits from the self instance.

In this commit, I am adding a new function remove() to the
bitmask_binop! macro. This function removes some set bits from the self
instance.

Signed-off-by: Uli Schlachter <[email protected]>
Copy link

codecov bot commented Nov 24, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (6078dd4) 12.70% compared to head (a84efb5) 12.72%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #904      +/-   ##
==========================================
+ Coverage   12.70%   12.72%   +0.01%     
==========================================
  Files         189      189              
  Lines      139726   139752      +26     
==========================================
+ Hits        17750    17779      +29     
+ Misses     121976   121973       -3     
Flag Coverage Δ
tests 12.72% <100.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@notgull notgull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to be, but does this cause any significant compile-time regression?

@psychon
Copy link
Owner Author

psychon commented Nov 24, 2023

but does this cause any significant compile-time regression?

Uhm... I looked at what #884 used for measurements and did it three times: for x in $(seq 1 3) ; do cargo clean && cargo build --no-default-features -F xfixes,randr,xkb,xinput ; done.

For master:

  • Finished dev [unoptimized + debuginfo] target(s) in 57.97s
  • Finished dev [unoptimized + debuginfo] target(s) in 57.95s
  • Finished dev [unoptimized + debuginfo] target(s) in 57.99s

For this branch:

  • Finished dev [unoptimized + debuginfo] target(s) in 57.82s
  • Finished dev [unoptimized + debuginfo] target(s) in 58.27s
  • Finished dev [unoptimized + debuginfo] target(s) in 58.06s

I'm not quite sure what do say from this... One of the branch builds was even faster.

Another round with -p x11rb-protocol added:

master:

  • 18.63s
  • 18.42s
  • 18.75s

This branch:

  • 18.66s
  • 18.62s
  • 19.24s

So... I guess the effect on build times is smaller than the noise here? But there might be an effect...

Copy link
Collaborator

@notgull notgull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good enough for me!

@mergify mergify bot merged commit 142ec2e into master Nov 24, 2023
23 checks passed
@mergify mergify bot deleted the bitflags-remove branch November 24, 2023 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants