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

Fix [Bug #20246]: Don't set next_head_exact if a capture is called #9897

Merged
merged 1 commit into from Feb 13, 2024

Conversation

makenowjust
Copy link
Contributor

@makenowjust makenowjust commented Feb 9, 2024

@bestwebua
Copy link

@makenowjust Thanks! 🔥

@makenowjust makenowjust merged commit 4a6384e into ruby:master Feb 13, 2024
98 checks passed
@makenowjust makenowjust deleted the fix-20246 branch February 13, 2024 00:53
nurse added a commit to nurse/ruby that referenced this pull request Mar 20, 2024
…Backport #20246]

	Clear all refined CCs on reopening refinement mod

	In cfd7729 we started using inline
	caches for refinements. However, we weren't clearing inline caches when
	defined on a reopened refinement module.

	Fixes [Bug #20246]

	Fix [Bug #20246]: Don't set next_head_exact if a capture is called (ruby#9897)
github-merge-queue bot pushed a commit that referenced this pull request Mar 21, 2024
…Backport #20246] (#10309)

Clear all refined CCs on reopening refinement mod

	In cfd7729 we started using inline
	caches for refinements. However, we weren't clearing inline caches when
	defined on a reopened refinement module.

	Fixes [Bug #20246]

	Fix [Bug #20246]: Don't set next_head_exact if a capture is called (#9897)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants