Repository navigation
Doc: clarify behavior of line-related functions - #27047
Merged
SolalPirelli merged 2 commits intoSep 10, 2026
Merged
Conversation
WojciechMazur
approved these changes
Sep 10, 2026
som-snytt
reviewed
Sep 10, 2026
| * output (i.e. output not terminated by a newline character) has | ||
| * to be made visible on the terminal. | ||
| * output (i.e. not ending in a line separator) has | ||
| * to be made visible. |
Contributor
There was a problem hiding this comment.
"visible" is also imprecise as well as biased.
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes https://users.scala-lang.org/t/which-line-separator-in-println/12375
This is still not quite right, because how it actually works is:
But it's better than referring to individual characters when there may be more than one.
Have you relied on LLM-based tools in this contribution?
No
How was the solution tested?
Non-code change, no tests needed