-
Notifications
You must be signed in to change notification settings - Fork 555
[nativeaot] fix typemap logic involving duplicates #9794
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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.
This will result in an ordering that is potentially different from what MonoVM has.
The problem is "aliases":
Mono.Android.dll
has them, too! For example, there are (at least) three bindings forjava/util/ArrayList
:Java.Util.ArrayList
Android.Runtime.JavaList
Android.Runtime.JavaList<T>
Which one "wins" currently?
Android.Runtime.JavaList
(non-generic). Why?TypeDefinition
ordering within the assembly:Is this a problem? ¯\(ツ)/¯. It's just what it is now, and generally the default doesn't necessarily matter, because you'll be going through an
Object.GetObject<T>()
invocation which will specify the appropriate type.Compare to what is done in the PR here: we have 3 candidate types, all in
Mono.Android.dll
, meaning we'll reverse the order. Thus, instead of preferringAndroid.Runtime.JavaList
, this code will instead preferJava.Util.ArrayList
.Again, is this a problem? I don't know, probably not? But it will be a change.
Is there a way to control the order of assemblies processed by the linker pipeline?
Looking at: https://github.com/dotnet/sdk/blob/a5393731b5b7b225692fff121f747fbbc9e8b140/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.ILLink.targets#L124-L156
It feels like if we change
@(ManagedAssemblyToLink)
so thatMono.Android.dll
is first, we'll get a similar result as what is done for MonoVM. Is it possible to reorder item group elements in that manner?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.
I updated the logic, so these assertions work now:
They did not previously work, but now I think the logic for NativeAOT is the same as described above.