[trimming] remove our usage of [Preserve]
#9126
Merged
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.
Fixes: #5197
[Preserve]
still works in some form, as theApplyPreserveAttribute
trimmer step will "mark" types it encounters. It unfortuantely, does not work if an assembly is deemed to be fully removed, as theApplyPreserveAttribute
will not be called for these types.To better align with the future of .NET, we should remove our usage of
[Preserve]
. The only failing result isJava.Lang.Object.SetHandleOnDeserialized
which can be preserved inMono.Android.xml
instead.In a future PR, we can consider emitting warnings in customer code with
[Preserve]
usage.