Skip to content
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

Run trim analyzer #65870

Merged
merged 9 commits into from
Mar 3, 2022
Merged

Run trim analyzer #65870

merged 9 commits into from
Mar 3, 2022

Conversation

sbomer
Copy link
Member

@sbomer sbomer commented Feb 25, 2022

No description provided.

@ghost
Copy link

ghost commented Feb 25, 2022

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

Issue Details

null

Author: sbomer
Assignees: sbomer
Labels:

area-Meta

Milestone: -

@sbomer sbomer added NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) and removed area-Meta labels Feb 25, 2022
using System.Runtime.CompilerServices;

namespace System.Reflection.Runtime.Dispensers
{
internal sealed class DispenserThatReusesAsLongAsKeyIsAlive<K, V> : Dispenser<K, V>
internal sealed class DispenserThatReusesAsLongAsKeyIsAlive<K, [DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.PublicParameterlessConstructor)] V> : Dispenser<K, V>
Copy link
Member Author

Choose a reason for hiding this comment

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

@MichalStrehovsky I'm not familiar enough with nativeaot to know why this wasn't warning (in the use of ConditionalWeakTable<K, V> below) in nativeaot - do you have any ideas?

Copy link
Member

Choose a reason for hiding this comment

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

IIRC warnings for generic dataflow are not implemented. I scoped out some of the warnings because it's not critical for functionality. One person working on dataflow part time on NativeAOT side is no match to several people working on this pretty much full time on the IL Linker side.

We'll be able to re-use the unit tests on the IL Linker side to bring this to parity once this becomes a priority.

@sbomer sbomer requested a review from vitek-karas March 3, 2022 00:47
@sbomer sbomer changed the title [WIP] Run trim analyzer Run trim analyzer Mar 3, 2022
@sbomer sbomer removed the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Mar 3, 2022
Use pragma instead of UnconditionalSuppressMessage
@sbomer
Copy link
Member Author

sbomer commented Mar 3, 2022

Failures are #66143

@sbomer sbomer merged commit 6246f84 into dotnet:main Mar 3, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Apr 3, 2022
@sbomer sbomer deleted the runTrimAnalyzer branch November 3, 2023 18:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants