-
Notifications
You must be signed in to change notification settings - Fork 439
Add diagnostic for unexpected second identifier #1382
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
Add diagnostic for unexpected second identifier #1382
Conversation
d2937be
to
a920e3c
Compare
ec8a8c5
to
df146f0
Compare
ecacd47
to
f965d6a
Compare
73bd9e8
to
f532d90
Compare
38bd131
to
582a48f
Compare
ec13f3d
to
618d2aa
Compare
c4b11b6
to
a68db20
Compare
d2190c7
to
3370247
Compare
29fcf4d
to
2e81b0a
Compare
2209414
to
6fd09dd
Compare
1d7d077
to
320d973
Compare
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.
Thank you. Looks good to me. Just one request for a comment
320d973
to
54a278e
Compare
@swift-ci please test |
@swift-ci please test windows |
1 similar comment
@swift-ci please test windows |
@swift-ci please test windows |
1 similar comment
@swift-ci please test windows |
It looks like windows is failing, can't figure out why? |
From the build log:
Looks like somehow a bad change was merged into LLDB or more likely a backport? I think that there is a branch mismatch. |
@swift-ci please test windows |
…-unexpected-second-identifier Add diagnostic for unexpected second identifier
…-unexpected-second-identifier Add diagnostic for unexpected second identifier
…-unexpected-second-identifier Add diagnostic for unexpected second identifier
…-unexpected-second-identifier Add diagnostic for unexpected second identifier
Part of fixing an TODOs in here: #1373
I just wanna ask if I'm on the right path.