Skip to content

Added printing arrays with java.lang.IO warning. - #9632

Open
gem-bricks wants to merge 1 commit into
apache:masterfrom
gem-bricks:io-array-printing-warning
Open

gem-bricks wants to merge 1 commit into
apache:masterfrom
gem-bricks:io-array-printing-warning

Conversation

@gem-bricks

@gem-bricks gem-bricks commented Sep 22, 2026

Copy link
Copy Markdown

java.lang.IO was added with JRE 25, which provides the alternative methods print and println. These delegate to the java.lang.System.out PrintStream, and currently, while array printing with out shows a warning, the IO methods do not.

Screenshot_20260921_205625

My pull request adds warnings for these methods. Using the hint has the same behavior as the System.out hints.


^Add meaningful description above

Click to collapse/expand PR instructions

By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -

  • are all your own work, and you have the right to contribute them.
  • are contributed solely under the terms and conditions of the Apache License 2.0 (see section 5 of the license for more information).

LLMs, Commit messages and PR description:

  • Please make sure (eg. git log) that all commits have a valid name and email address for you in the Author field.
  • LLM assisted commits should be attributed with an Assisted-by: MODEL_NAME MODEL_VERSION line appended to the commit message.
    • Please mention coding assistance in the PR description too (eg. by adding the same Assisted-by line from above)
    • Please describe the changes in your own words - we'd like to know you understand the changes being made!

If you're a first time contributor, see the Contributing guidelines for more information.

If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.

PR approval and merge checklist:

  1. Was this PR correctly labeled, did the right tests run? When did they run?
  2. Is this PR squashed?
  3. Are author name / email address correct? Are co-authors correctly listed? Do the commit messages need updates?
  4. Does the PR title and description still fit after the Nth iteration? Is the description sufficient to appear in the release notes?

If this PR targets the delivery branch: don't merge. (full wiki article)

@gem-bricks
gem-bricks force-pushed the io-array-printing-warning branch from 0a9fcda to bcfeca7 Compare September 22, 2026 03:12
@gem-bricks

Copy link
Copy Markdown
Author

Tests for java.hints passed

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.

1 participant