-
Notifications
You must be signed in to change notification settings - Fork 696
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
- Loading branch information
Showing
3 changed files
with
39 additions
and
8 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
synopsis: Add LexBraces lexer warning | ||
packages: Cabal-syntax | ||
issues: #8577 | ||
|
||
description: { | ||
|
||
LexBraces warning is issued when brace delimiting syntax is used. | ||
This way, using `readFields'`, a low-lever consumer may decide | ||
whether braces were used. | ||
|
||
(Looking for a brace character in the input is imprecise, as braces can occur inside field content). | ||
|
||
This warning is not propagated to parser warnings, | ||
so e.g. readGenericPackageDescription doesn't warn about it. | ||
This is because all parser warnings prevent uploads to Hackage, | ||
and using braces (or not) is opinionated choice. | ||
|
||
} |