Handle plugin-private stack types in callsite binder#29096
Merged
Conversation
wendigo
approved these changes
Apr 14, 2026
Member
Please replace |
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.
A plugin can provide a type with a Java class stack type that is only visible in the plugin. These types can not be used directly in code generated by the engine because the generated code is loaded in a class loader that cannot see these private types. In this case we need to change the stack type in the generated code to
Objectand adapt any function to useObjectinstead of the private stack type. We only apply this adaptation for private stack types, to keep generated code more readable.Fixed #29093
Release notes
(x) Release notes are required, with the following suggested text: