#1589 Move Parsers:2177 err to new format #2919
Merged
Conversation
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
Closed
| val kind = "Syntax" | ||
| val msg = "expected start of definition" | ||
| val explanation = | ||
| hl"you have to provide either ${"class"}, ${"object"}, or ${"enum"} definitions after qualifiers" |
Contributor
|
Otherwise LGTM |
lorandszakacs
force-pushed
the
errmsg/lorandszakacs_parser_2177
branch
from
041534c to
72c123d
Compare
Contributor
Author
|
@nicolasstucki, thanks! I updated it. |
Contributor
|
Thanks |
nicolasstucki
approved these changes
Jul 28, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Move error for
Parsers:2177to new format.Actual line numbers have started getting out of sync with the description in issue #1589. But it should be quite straightforward to see that this was also necessary.