fix: correct type reference for ClassLiteralAccess #4383
Merged
Conversation
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
MartinWitt
changed the title
|
LGTM. The two last tests are identical? |
|
Oh, sorry on test should be an unqualified Type Reference, I changed it. |
monperrus
changed the title
|
thanks @doukai for the bug report and @MartinWitt for the fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fix #4350
This should the fix issue #4350 . I tried to create an as small class as possible for the test case. The testcase seems pretty bad, any suggestions for an assertion checking if a String equals without newline characters? Otherwise, the new testcase is again Unix only.