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

bb = usize::MAX isn't a special value. #964

Merged
merged 1 commit into from
Feb 8, 2024

Conversation

ltratt
Copy link
Contributor

@ltratt ltratt commented Feb 8, 2024

At some point in the past bb = usize::MAX was used to represent "unmappable" but it's now a separate enum item. Nowhere in yk seems to check/set bb for/to usize::MAX so this commit removes the (hopefully) misleading comment. In case we're wrong, I've left behind an assert that's likely to catch any old code. One day far in the future our successors might feel confident enough to remove the assert!

At some point in the past `bb = usize::MAX` was used to represent
"unmappable" but it's now a separate `enum` item. Nowhere in yk seems to
check/set `bb` for/to `usize::MAX` so this commit removes the
(hopefully) misleading comment. In case we're wrong, I've left behind an
`assert` that's likely to catch any old code. One day far in the future
our successors might feel confident enough to remove the `assert`!
@vext01 vext01 added this pull request to the merge queue Feb 8, 2024
@vext01 vext01 removed this pull request from the merge queue due to a manual request Feb 8, 2024
@vext01 vext01 added this pull request to the merge queue Feb 8, 2024
Merged via the queue into ykjit:master with commit 7443540 Feb 8, 2024
2 checks passed
@ltratt ltratt deleted the remove_outdated_comment branch March 30, 2024 09:13
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