Skip to content

Make the user code range detection more robust. #8694

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
May 6, 2024

Conversation

adrian-prantl
Copy link

While it could be determined statically, it's more future-proof to calculate it every time, since some substituions might intrroduce extra newlines.

rdar://127123509

@adrian-prantl
Copy link
Author

@swift-ci test

Copy link

@felipepiovezan felipepiovezan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! (the bot failures might be real though?)

While it could be determined statically, it's more future-proof to
calculate it every time, since some substituions might intrroduce
extra newlines.

rdar://127123509
@adrian-prantl
Copy link
Author

Give how wrong the last iteration was (it counted characters instead of lines), I'm impressed it only broke one test.

@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl adrian-prantl merged commit b18f7e6 into swiftlang:swift/release/6.0 May 6, 2024
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.

2 participants