Skip to content

Rename is_bit_clear to bit_is_clear, is_bit_set to bit_is_set #111

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

Merged
merged 1 commit into from
Jun 11, 2017

Conversation

adamgreig
Copy link
Member

Ugh, I know we just merged #109 but after using it for a couple of days I think it really should have been bit_is_set() rather than is_bit_set(). I'm happy with set_bit() and clear_bit() though, they seem natural:

usart3.cr3.dmat().set_bit();
while usart3.isr().tc().bit_is_clear() {}

if usart3.isr().ore().bit_is_set() {
    ...
}

As an added bonus, this way around we don't have to reserve the bit_set/bit_clear variant names, because it will no longer clash.

What do you think?

@japaric
Copy link
Member

japaric commented Jun 10, 2017

LGTM.

we don't have to reserve the bit_set/bit_clear variant names

👍

@whitequark Any opinion on this PR?

@whitequark
Copy link
Contributor

@japaric No objection

@japaric
Copy link
Member

japaric commented Jun 11, 2017

@homunkulus r+

@homunkulus
Copy link
Contributor

📌 Commit 718645c has been approved by japaric

@homunkulus
Copy link
Contributor

⌛ Testing commit 718645c with merge 718645c...

@homunkulus
Copy link
Contributor

☀️ Test successful - status-appveyor, status-travis
Approved by: japaric
Pushing 718645c to master...

@homunkulus homunkulus merged commit 718645c into rust-embedded:master Jun 11, 2017
@adamgreig adamgreig deleted the rename_is_bit_set branch May 5, 2019 21:36
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.

4 participants