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
[SR-14221] Add tricky parsing test case. #56597
Comments
Feel free to ping me on GitHub for review (@ varungandhi-apple), or ask questions here. |
@swift-ci create |
Comment by Hongjing Chen (JIRA) Hello, can I try to work on this as my first contribution? theindigamer (JIRA User) Hope I don't misunderstand what you mean. I have some quetions. The correct thing is that the code should be regareded as a trailing closure, right? Do we expect an error to occur when testing? |
Yes, that's correct.
We don't expect any error to happen during testing, but the reason to add the test case (in case it doesn't exist already) is to avoid regressing this edge case when changing the parser. Sometimes one might forget to realize all the edge cases that one needs to consider, and make some change assuming that it won't break anything, but in reality there is some edge case which does break. So it's helpful to have tests for edge cases even if the code is working alright. |
Comment by Hongjing Chen (JIRA) Thanks. I’ll check if it needs to be added. |
PR opened by Hongjing: #36202 |
theindigamer (JIRA User), can this be closed now since the PR has been merged? |
Thanks Stefano, yeah, we can close this. |
Additional Detail from JIRA
md5: 7a6db14dd0d359bf7788331e075f0452
Issue Description:
This is interpreted as a trailing closure, instead of being interpreted as an error where you are trying to have a computed property with an initial value (computed properties don't have initial values).
We should check if the test/Parse directory has a test case which checks for this. If not, we should add this test case and leave a comment indicating why this test case is present.
The text was updated successfully, but these errors were encountered: