mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-10-06 23:26:55 +01:00
Applies NKarolak's review suggestion: a case value set needs no parentheses around a comparison. Encodes the rationale in the Best Practice section, since it is a real advantage of the pattern and is not documented elsewhere in the repo. The AL operator hierarchy places and/xor above the comparison operators and or just above them too, so parentheses are mandatory in an and chain — A = B and C = D misparses without them — while a case value set has no and to bind tighter and needs none. That inverts the precedence most developers arrive with from C#. Also notes in the bad sample that its parentheses are not optional, so the two samples contrast on parentheses as well as on evaluation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| boolean-operators-do-not-short-circuit.bad.al | ||
| boolean-operators-do-not-short-circuit.good.al | ||
| boolean-operators-do-not-short-circuit.md | ||
| case-true-of-for-long-condition-chains.bad.al | ||
| case-true-of-for-long-condition-chains.good.al | ||
| case-true-of-for-long-condition-chains.md | ||