IO.print without new line

[JaroslavTulach]

Pull Request Description

Fixes #10028 by adding IO.print function that doesn't add new line at the end of its message.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.

[radeusgd]

Please let's not use such shorthands in our public (1) API. I'd suggest to call this argument newline or we could do similar to Python: end or perhaps a more explicit end_with = '\n' (I think I like end_with the most, but that's just subjective).

Also the documentation should be updated to include the added argument in the Arguments: section.

(1) The PRIVATE comment at the top may be confusing. It is used there to prevent a text-oriented method from showing up in the GUI's component browser. But the println method is definitely part of our 'official' API and so it should be well documented for end-users. As already mentioned we probably should create a separate tag, like TEXT_ONLY or HIDDEN, for documenting components that are not internal but should not show up in the GUI Component Browser.

[farmaazon]

My twopence: if println does not end necessarily with newline, it should be called print (as it is in python).

[Akirathan]

My twopence: if println does not end necessarily with newline, it should be called print (as it is in python).

I agree. Why not have two methods - IO.println and IO.print just like in dozens of other languages?

[radeusgd]

My twopence: if println does not end necessarily with newline, it should be called print (as it is in python).

Fair point. I'd suggest that we keep println as-is (without adding any new optional arguments) and then add print variant that does not append any newlines (again it would not need additional arguments).

This way we can keep using println as-is - as we are using it with the default newline in 99% of the codebase; and in places where we need no newline we can use print instead (which is currently just a single place).

IMO separating into two functions would be clearest. And it's already done that way e.g. in Java, so people will be familiar with it.

[4e6]

I agree with Adam. IMO the function should've been called print from the beginning.

[JaroslavTulach]

I agree with Adam. IMO the function should've been called print from the beginning.

The problem with Adam's rename to print is that such a change is backward incompatible. Easier to just

we keep println as-is (without adding any new optional arguments) and then add print variant that does not append any newlines (again it would not need additional arguments).

As proposed by @radeusgd and voted up by @GregoryTravis, @hubertp and @Akirathan. I'll prepare the patch.

[JaroslavTulach]

CRLF failure on Windows will be fixed by 7e8feee