Improve diagnostics marked with TODO in Tests/SwiftParser/translated

[ahoppen]

There are ~150 TODOs left in the test cases where diagnostics from the C++ parser are superior to the ones generated by SwiftParser. Those should be fixed.

Some of these TODOs are marked as “good first issue” and fixing those should be a good starting point to get started with the swift-syntax codebase.

Here’s a list of the tests that still have TODOs remaining. If you’ve got commit access to the repository and are working on one of them, mark them as ticked and add your named to assign them to you. If you don’t have commit access, comment on this issue and I’ll update the list to assign an issue to you.

• testAvailabilityQueryUnavailability34a @CippoX
• testDiagnoseAvailability17 @kimdv
• testDiagnoseAvailability20 @kimdv
• testDiagnoseAvailability21 @kimdv
• testEffectfulProperties12 @StevenWong12
• testEffectfulProperties13 @StevenWong12
• testIfconfigExpr17
• testIfconfigExpr22
• testIfconfigExpr24
• testIfconfigExpr25
• testIfconfigExpr27
• testIfconfigExpr28
• testIfconfigExpr30
• testOperatorDecl6 @StevenWong12
• testOperatorDecl7 @StevenWong12
• testOperatorDecl8 @StevenWong12
• testOperatorDecl21 @StevenWong12
• testRecovery17
• testRecovery19
• testRecovery23
• testRecovery25
• testRecovery28
• testRecovery49
• testRecovery63 (good first issue)
• testRecovery64 (good first issue)
• testRecovery98c @kimdv
• testRecovery98d @kimdv
• testRecovery98e @kimdv
• testRecovery98f @kimdv
• testRecovery98 @kimdv
• testRecovery99 @kimdv
• testRecovery100 @kimdv
• testRecovery10
• testRecovery102 @CippoX
• testRecovery103@CippoX
• testRecovery104@CippoX
• testRecovery110 @kimdv
• testRecovery121 @kimdv
• testRecovery125 @kimdv
• testRecovery126 @kimdv
• testRecovery127 @kimdv
• testRecovery128 @kimdv
• testRecovery129 @kimdv
• testRecovery130 @kimdv
• testRecovery131 @kimdv
• testRecovery136 @ahoppen
• testRecovery137 @ahoppen
• testRecovery151 @kimdv
• testRecovery153 @kimdv
• testRecovery157 @CippoX
• testRecovery163 @kimdv
• testRecovery164 @kimdv
• testRecovery165
• testRecovery169
• testRecovery176 @kimdv
• testRecovery177 @kimdv
• testRecovery181
• testTrailingClosures14

[ahoppen]

rdar://106083939

[Rajveer100]

Hey @ahoppen, what are the additional codebase setup requirements apart from the swift-compiler setup which I already have, so I can start contributing to this repo too!

[bbvch13531]

Hello! I'm currently working on testAvailabilityQuery34 in AvailabilityQueryTests.swift

Could I create a new issue and if there are few questions about this TODO? @ahoppen

[kimdv]

Hi!

I'm looking into testIdentifiers7

[ahoppen]

Hey @ahoppen, what are the additional codebase setup requirements apart from the swift-compiler setup which I already have, so I can start contributing to this repo too!

SwiftSyntax is (mostly) a standalone repo for which you don't need to build the Swift compiler yourself. You should be able to just open it in Xcode or in any other editor that supports LSP with SourceKit-LSP such as VSCode with the Swift Extension.

[ahoppen]

To anyone who starts working on an issue, if you've gotten so far that you can open a PR (even if there are still things that don't work) we can use that to discuss further questions. If you need help before you've made any significant code changes, I agree that opening a new issues is a good way to keep the discussions focussed.

[CippoX]

Hi everyone, I'm working on testRecovery64

[ahoppen]

@CippoX, @kimdv is already working on testRecovery64 here #1382

[CippoX]

@bbvch13531 are you still on testAvailabilityQuery34? Or is anyone looking into testAvailabilityQueryUnavailability28 or testAvailabilityQueryUnavailability34a?

[ahoppen]

@CippoX

I don’t know of anyone working on testAvailabilityQueryUnavailability34a, if you want to take a look at that, that’d be great.

I suspect that testAvailabilityQueryUnavailability28 requires the same fix as testAvailabilityQuery34, so I’d like to see if @bbvch13531 is still working on it.

[CippoX]

Thank you @ahoppen, since @bbvch13531 didn't respond I've already made a pull request #1423, I'm also looking at testAvailabilityQueryUnavailability34a

[ahoppen]

@CippoX, Oh, sorry, I didn’t see that PR yet while going through my emails. Thanks for creating it. 👍🏽

[CippoX]

Hi, I'm working on testRecovery176

[ahoppen]

@CippoX I’m sorry @kimdv beat you to it: #1445

@kimdv Could you add comments here if you’re working on one of the TODOs to avoid these conflicts? It’s fine if you just have one comment and update that as well.

Edit: I changed my mind and am now keeping a list in the issue description. @kimdv Feel free to assign failing test cases to yourself if you want to.

[CippoX]

Thanks, we already solved it 👍