-
Notifications
You must be signed in to change notification settings - Fork 571
[TrimmableTypeMap] Remove InvokerType from JavaPeerProxy #11971
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
Open
simonrozsival
wants to merge
5
commits into
main
Choose a base branch
from
android-trimmable-remove-invoker-type
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c32f19d
[TrimmableTypeMap] Remove InvokerType from JavaPeerProxy
simonrozsival 1eebaaa
[TrimmableTypeMap] Stop emitting InvokerType in the generator
simonrozsival d704055
[TrimmableTypeMap] Update tests for removed InvokerType
simonrozsival 3a7ceb0
[TrimmableTypeMap] Address code review feedback
simonrozsival e9647b2
[TrimmableTypeMap] Test emitted proxy .ctor base-ctor arity
simonrozsival File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 💡 Testing — This is the crux of the change: the generated
.ctornow calls the base ctor with arity2/1instead of3/2. ButTypeMapAssemblyGeneratorTestsonly assert that a.ctorexists by name (Assert.Contains (".ctor", methods)) and thatctorRefs.Count >= 2— none of them decode the emitted.ctorbody. A base-ctor arity/token mismatch here would sail past metadata inspection and only surface as anInvalidProgramException/TypeLoadExceptionon the CoreCLR device legs. There's already precedent for body-level decoding (AssertCreateInstanceReturnsNull, and the JI-ctor signature decode), so consider asserting that the emitted.ctorinvokes the base ctor with the expected arity for both the generic (concrete) and non-generic (interface/open-generic) paths. Not blocking — the device legs cover it at runtime.Rule: Generator tests should validate emitted IL bodies, not just member presence
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call — addressed in e9647b2. Added
Generate_ProxyCtor_ChainsToExpectedBaseConstructor, a[Theory]that decodes the emitted.ctorbody and asserts it chains to the expected base ctor for all three paths:JavaPeerProxy<T>base, arity 1(string), noGetTypeFromHandle;JavaPeerProxybase, arity 2(string, Type), with aType.GetTypeFromHandlecall;It resolves the
calltoken to the base-ctorMemberRefand decodes its signature arity (reusingReadCallTokens/TypeNameSignatureDecoder), so an arity/token mismatch now fails in-suite instead of only on the device legs. 608/608 passing.