Conversation
Author
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.
Summary
For an assignment to a non-String variable, such as
Object v = "a"; v += "b";, javac emits an indy string concatenation whose call type returnsObject.The GraalVM
OutlineIndyStringConcatPlugincopied that return type.Then in
OutlinedSBMethod.buildGraph, due toObject, the method when intoSubstrateSBConcatFactoryinstead and the image build failed.(With
should not reach here: unexpected input could not be handled: class java.lang.Object).The return type is now always
String, as a string concatenation always produces aString.Then, the code will instead go to the
SubstrateStringConcatFactory, which is correct and will work correctly.Related Issues
Fixes: #14533
Testing
Documentation
Contributor Checklist