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

Don't assume that Qfalse is 0 in rb_special_const_p #1139

Merged
merged 1 commit into from
Feb 27, 2024

Conversation

peterzhu2118
Copy link
Member

rb_special_const_p returns a VALUE (Qtrue or Qfalse), so can directly return the value and we shouldn't assume that Qfalse is 0.

rb_special_const_p returns a VALUE (Qtrue or Qfalse), so can directly
return the value and we shouldn't assume that Qfalse is 0.
@eregon eregon merged commit 408e230 into ruby:master Feb 27, 2024
13 checks passed
@peterzhu2118 peterzhu2118 deleted the special-const branch February 27, 2024 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants