Skip to content

[Diagnostics] Stop using unicode line characters #2581

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
Apr 2, 2024

Conversation

rintaro
Copy link
Member

@rintaro rintaro commented Apr 1, 2024

ASCII characters are more reliable.

┆    → :
│    → |
├─   → |-
╰─   → `-
╭───   +---
│    → |
╰───   +---

ASCII characters are more reliable.
@rintaro rintaro requested review from ahoppen and bnbarham as code owners April 1, 2024 22:19
@rintaro
Copy link
Member Author

rintaro commented Apr 1, 2024

@swift-ci Please test

@bnbarham
Copy link
Contributor

bnbarham commented Apr 1, 2024

This makes me a little sad, but given the issues we've had across various platforms... IMO it seems like the most reasonable route to take for now.

@rintaro
Copy link
Member Author

rintaro commented Apr 2, 2024

swiftlang/swift#72754
@swift-ci Please test

@rintaro rintaro merged commit 55c4e46 into swiftlang:main Apr 2, 2024
@Matejkob
Copy link
Contributor

Matejkob commented Apr 4, 2024

This makes me a little sad, but given the issues we've had across various platforms... IMO it seems like the most reasonable route to take for now.

Why not use different annotation characters based on the context?

@DougGregor
Copy link
Member

Why not use different annotation characters based on the context?

Unfortunately, we don't really have enough context. We could try to detect when we're in a terminal, but some terminals handle Unicode properly and some do not. And when we're emitting diagnostics to a file, we have no notion of whether the tool reading that file will handle Unicode. So at best, we'd be able to introduce the Unicode in a few places where we know it would work... but then folks would be surprised at the output differing in different environments.

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.

4 participants