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

Fill in FeatureCheckDataflow.cs assertions with issue links #102679

Merged
merged 5 commits into from
Jun 4, 2024

Conversation

jtschuster
Copy link
Member

Adds issues links / explanations to FeatureCheckDataflow, and a couple other places.

I couldn't find the issue for the linker and NativeAOT not being able to handle more complex boolean operations with feature switches. Please let me know if you know if the issue does / doesn't exist and I'll link it / make one.

@jtschuster jtschuster requested a review from sbomer May 24, 2024 23:57
@jtschuster jtschuster requested a review from marek-safar as a code owner May 24, 2024 23:57
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label May 24, 2024
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label May 24, 2024
@@ -337,7 +337,7 @@ static void And ()
}
Copy link
Member Author

@jtschuster jtschuster May 24, 2024

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

Currently we treat this as expected behavior based, described at https://github.com/dotnet/runtime/blob/main/docs/design/tools/illink/feature-checks.md#boolean-andor, but I think we could file an issue to track it and reference that here.

Copy link
Member Author

Choose a reason for hiding this comment

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

Made #102830 to track unifying behavior on this.

@@ -337,7 +337,7 @@ static void And ()
}
Copy link
Member

Choose a reason for hiding this comment

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

Currently we treat this as expected behavior based, described at https://github.com/dotnet/runtime/blob/main/docs/design/tools/illink/feature-checks.md#boolean-andor, but I think we could file an issue to track it and reference that here.

Copy link
Member

@sbomer sbomer left a comment

Choose a reason for hiding this comment

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

Thank you!

@jtschuster jtschuster added area-Tools-ILLink .NET linker development as well as trimming analyzers and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Jun 3, 2024
Copy link
Contributor

Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas
See info in area-owners.md if you want to be subscribed.

@jtschuster
Copy link
Member Author

/ba-g This only changes trimmer tests. Trimmer tests are passing and failures are unrelated.

@jtschuster jtschuster merged commit 40ff2ec into dotnet:main Jun 4, 2024
68 of 76 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jul 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Tools-ILLink .NET linker development as well as trimming analyzers linkable-framework Issues associated with delivering a linker friendly framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants