You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
- There is a valid warning of potentially misuse of comma operator in match function.
Solution:
- Use semicolon instead of comma to avoid the warning and make the intend cleaner.
- Add gherkin unit test to verify the behaviour of match in an integration test.
Problem:
- There is a valid warning of potentially misuse of comma operator in match function.
Solution:
- Use semicolon instead of comma to avoid the warning and make the intend cleaner.
- Add gherkin unit test to verify the behaviour of match in an integration test.
Problem:
- There is a valid warning of potentially misuse of comma operator in match function.
Solution:
- Use semicolon instead of comma to avoid the warning and make the intend cleaner.
- Add gherkin unit test to verify the behaviour of match in an integration test.
This is more of a question than a bug report, as I haven't managed to narrow down my configuration enough to give you a minimal repro.
The question is: is the comma operator in this code intentional, and if so, could a static cast be added to silence the warning?
In some of my builds, where I treat warnings as errors, I am getting this:
Specifications
The text was updated successfully, but these errors were encountered: