Rename check() to check_for()
#498
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bad news: `check(TRUNCATION_RISK)` won't work if the user's namespace has a `check` namespace. Aurora does; that's how I found out. Not a huge deal: we can rename `check()` to `guard_against()`. This isn't quite as concise, but it reads very nicely, and is extremely unlikely to be a namespace anywhere out in the wild (which I think is also true of `ignore`. Follow-up to #387.
chiphogg
changed the title
check() to guard_against()check() to check_for()
hoffbrinkle
approved these changes
Aug 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bad news:
check(TRUNCATION_RISK)won't work if the user's namespacehas a
checknamespace. Aurora does; that's how I found out.Not a huge deal: we can rename
check()tocheck_for(). This isn'tquite as concise, but it reads very nicely, and is extremely unlikely to
be a namespace anywhere out in the wild (which I think is also true of
ignore.Follow-up to #387.