Skip to content

Conversation

@MichalStrehovsky
Copy link
Member

DynamicallyAccessedMemberTypes.All can be replaced with the newly added AllMethods since it has the right semantics (keep privates in base types).

Cc @dotnet/illink @eerhardt

@MichalStrehovsky MichalStrehovsky added the linkable-framework Issues associated with delivering a linker friendly framework label Nov 13, 2024
@ghost
Copy link

ghost commented Nov 13, 2024

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

1 similar comment
@ghost
Copy link

ghost commented Nov 13, 2024

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-reflection
See info in area-owners.md if you want to be subscribed.

Copy link
Member

@eerhardt eerhardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Thanks!

Are there any upstream callers that can be changed from All to AllMethods? I’m not sure an easy way to check. It might be nice if the analyzer had an option to alert when you are preserving too much.

@MichalStrehovsky
Copy link
Member Author

Are there any upstream callers that can be changed from All to AllMethods?

I did a search in this repo - we don't use these overloads.

I’m not sure an easy way to check. It might be nice if the analyzer had an option to alert when you are preserving too much.

Yup, would be a nice feature! Cc @dotnet/illink

@MichalStrehovsky
Copy link
Member Author

/ba-g the only not-known-issues are timeouts in unrelated tests

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-System.Reflection linkable-framework Issues associated with delivering a linker friendly framework new-api-needs-documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants