Skip to content

should use owned_p instead of locked_p #3949

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Dec 20, 2020
Merged

should use owned_p instead of locked_p #3949

merged 1 commit into from
Dec 20, 2020

Conversation

ko1
Copy link
Contributor

@ko1 ko1 commented Dec 20, 2020

It should raise an error if the same thread tris to call
receive/receive_if.

@ko1
should use owned_p instead of locked_p
af13114 
It should raise an error if the same thread tris to call
receive/receive_if.
@ko1 ko1 force-pushed the fix_ractor_receive_if_recursive_check branch from a306a15 to af13114 Compare December 20, 2020 17:18
@ko1 ko1 merged commit 6be61ab into ruby:master Dec 20, 2020
@ko1 ko1 deleted the fix_ractor_receive_if_recursive_check branch December 21, 2020 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ko1