Uh oh!
There was an error while loading. Please reload this page.
add RangeToExclusivePattern to the reference - #1746
Closed
m4rch3n1ng wants to merge 1 commit into
Closed
Conversation
ehuss
commented
Mar 12, 2025
Contributor
Thanks for the PR! I started looking at fixing some other issues, and then as I started to tug on the threads it started to unravel, so I have moved my work over to #1756. |
rustbot
commented
Mar 18, 2025
Collaborator
☔ The latest upstream changes (possibly 9e24743) made this pull request unmergeable. Please resolve the merge conflicts. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
they were stabilized alongside the other exclusive patterns, but were missed by #1484, presumably because they were not mentioned on the tracking issue, presumably because they were also part of another feature and were not added to the other tracking issue after that feature was stabilized.