Skip to content

ci in iseq can only be object or null #7147

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
Jan 19, 2023

Conversation

peterzhu2118
Copy link
Member

It looks like rb_callinfo in iseq can only be either a Ruby object or null, since it cannot be allocated on the stack.

It looks like rb_callinfo in iseq can only be either a Ruby object or
null, since it cannot be allocated on the stack.
@peterzhu2118 peterzhu2118 merged commit dcc676a into ruby:master Jan 19, 2023
@peterzhu2118 peterzhu2118 deleted the pz-iseq-ci-null branch January 19, 2023 14:47
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