Add regression test: #7177, never-matched warning FS0026 with active patterns#19528
Merged
Add regression test: #7177, never-matched warning FS0026 with active patterns#19528
Conversation
Fixes #7177 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Mar 31, 2026
T-Gro
approved these changes
Apr 1, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 #7177
Adds a regression test verifying that
FS0026("This rule will never be matched") is correctly emitted when an active pattern precedes unreachable wildcard match rules. This was previously not reported due to howwarnOnUnusedwas disabled for "problematic" clauses — the fix is now inmain.Test added:
ErrorMessages.DiagnosticRegressionTests—Issue 7177 - never matched warning FS0026 is emitted when active pattern precedes wildcard rules