Skip to content

Conversation

hamishknight
Copy link
Contributor

5.7 cherry-pick of #535

Adjust the upper bound of the Range down when forming the quantification, as it expects an inclusive upper bound. Additionally, upgrade a couple of assertions to preconditions to ensure we don't silently fail byte code emission.

Resolves #478

Adjust the upper bound of the Range down when
forming the quantification, as it expects an
inclusive upper bound.
Seems like we ought to crash in a release build
instead of potentially crashing during byte code
emission or silently failing to match.
@hamishknight hamishknight added the r5.7 5.7 Release Cherry Picks label Jul 1, 2022
@hamishknight
Copy link
Contributor Author

@swift-ci please test

@hamishknight hamishknight merged commit be98b28 into swiftlang:swift/release/5.7 Jul 1, 2022
@hamishknight hamishknight deleted the one-more-5.7 branch July 1, 2022 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

r5.7 5.7 Release Cherry Picks

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants