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

Rename Mutex and Cond methods for consistency #111

Merged
merged 1 commit into from
Sep 7, 2024

Conversation

tchajed
Copy link
Member

@tchajed tchajed commented Sep 7, 2024

Previously, the names acquire/release and acquire_spec/release_spec came from HeapLang, and mutexes were the only place this convention was used.

For consistency with how we typically name functions and specs (and to match Go), this commit renames to Mutex__Lock and wp_Mutex__Lock, and similarly for Unlock. At the same time we make the Cond methods more consistent with this convention, although its specs already used the wp_ naming style.

Previously, the names acquire/release and acquire_spec/release_spec came
from HeapLang, and mutexes were the only place this convention was used.

For consistency with how we typically name functions and specs (and to
match Go), this commit renames to `Mutex__Lock` and `wp_Mutex__Lock`,
and similarly for Unlock. At the same time we make the Cond methods more
consistent with this convention, although its specs already used the
`wp_` naming style.
@tchajed
Copy link
Member Author

tchajed commented Sep 7, 2024

I've already made the changes to goose locally and will push that and update the goose output once this merges.

@tchajed tchajed merged commit 90480d0 into master Sep 7, 2024
6 checks passed
@tchajed tchajed deleted the tchajed/rename-mutex-methods branch September 7, 2024 18:25
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.

1 participant