Skip to content
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

Optimize string format #1346

Merged
merged 1 commit into from
Nov 30, 2016
Merged

Optimize string format #1346

merged 1 commit into from
Nov 30, 2016

Conversation

smallyard
Copy link
Contributor

In format strings, it is generally preferable better to use %n, which will produce the platform-specific line separator.

 In format strings, it is generally preferable better to use %n, which will produce the platform-specific line separator.
@smallyard smallyard changed the title optimize string format Optimize string format Jul 18, 2016
@marcphilipp
Copy link
Member

I don't have a strong opinion about this one.

@junit-team/junit-lambda What do you think?

@marcphilipp
Copy link
Member

Oops, I mistook this issue for an opentest4j one (now there is one over there, too: ota4j-team/opentest4j#24).

@junit-team/junit-committers What do you think about this one?

@kcooney
Copy link
Member

kcooney commented Jul 24, 2016

The commit message is a bit weird (this isn't an optimizationn) but we can fix that when we merge the commit if we use hub. The change is fine

@kcooney kcooney merged commit 638e824 into junit-team:master Nov 30, 2016
@stefanbirkner stefanbirkner added this to the 4.13 milestone Nov 30, 2016
sebasjm pushed a commit to sebasjm/junit4 that referenced this pull request Mar 11, 2018
In format strings, it is generally preferable better to use %n, which will produce the platform-specific line separator.
aristotle0x01 pushed a commit to aristotle0x01/junit4 that referenced this pull request Jun 27, 2022
In format strings, it is generally preferable better to use %n, which will produce the platform-specific line separator.
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