-
Notifications
You must be signed in to change notification settings - Fork 786
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
Warnings for invalid #nowarn arguments #17871
Conversation
❗ Release notes required
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few comments inline
tests/FSharp.Compiler.ComponentTests/CompilerDirectives/NonStringArgs.fs
Show resolved
Hide resolved
tests/FSharp.Compiler.ComponentTests/CompilerDirectives/NonStringArgs.fs
Outdated
Show resolved
Hide resolved
tests/FSharp.Compiler.ComponentTests/CompilerDirectives/NonStringArgs.fs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good now, thank you for your patience with this PR!
Co-authored-by: Petr Pokorny <petr@innit.cz>
Head branch was pushed to by a user without write access
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
Commenter does not have sufficient privileges for PR 17871 in repo dotnet/fsharp |
This is ready |
Description
Fixes #17870
Also centralizes the distributed logic for processing #nowarn arguments, for better maintainability.
Checklist