Is the order of precedence for logical operators the same as

Question

Is the order of precedence for logical operators the same as in Java Is there a program someone has written to show what is the order of execution for a statement like ```a == b amp amp c || a == d amp amp e```

ephemient · Answer

yes <https kotlinlang org docs reference grammar html expressions>

ephemient · Answer

you could possibly use <https github com kotlinx ast> to parse and print the groupings of the expression but I m not aware of anything pre built

ephemient · Answer

```$ kotlin parse main kts a == b amp amp c || a == d amp amp e packageHeader functionDeclaration FUN gt gt gt fun lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN simpleIdentifier Identifier gt gt gt main lt lt lt DEFAULT TOKEN CHANNEL functionValueParameters LPAREN gt gt gt lt lt lt DEFAULT TOKEN CHANNEL RPAREN gt gt gt lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN functionBody block LCURL gt gt gt lt lt lt DEFAULT TOKEN CHANNEL NL gt gt gt n lt lt lt DEFAULT TOKEN CHANNEL statements statement expression disjunction conjunction equality comparison genericCallLikeComparison infixOperation elvisExpression infixFunctionCall rangeExpression additiveExpression multiplicativeExpression asExpression prefixUnaryExpression postfixUnaryExpression primaryExpression simpleIdentifier Identifier gt gt gt a lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN equalityOperator EQEQ gt gt gt == lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN comparison genericCallLikeComparison infixOperation elvisExpression infixFunctionCall rangeExpression additiveExpression multiplicativeExpression asExpression prefixUnaryExpression postfixUnaryExpression primaryExpression simpleIdentifier Identifier gt gt gt b lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN CONJ gt gt gt amp amp lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN equality comparison genericCallLikeComparison infixOperation elvisExpression infixFunctionCall rangeExpression additiveExpression multiplicativeExpression asExpression prefixUnaryExpression postfixUnaryExpression primaryExpression simpleIdentifier Identifier gt gt gt c lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN DISJ gt gt gt || lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN conjunction equality comparison genericCallLikeComparison infixOperation elvisExpression infixFunctionCall rangeExpression additiveExpression multiplicativeExpression asExpression prefixUnaryExpression postfixUnaryExpression primaryExpression simpleIdentifier Identifier gt gt gt a lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN equalityOperator EQEQ gt gt gt == lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN comparison genericCallLikeComparison infixOperation elvisExpression infixFunctionCall rangeExpression additiveExpression multiplicativeExpression asExpression prefixUnaryExpression postfixUnaryExpression primaryExpression simpleIdentifier Identifier gt gt gt d lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN CONJ gt gt gt amp amp lt lt lt DEFAULT TOKEN CHANNEL WS gt gt gt lt lt lt HIDDEN equality comparison genericCallLikeComparison infixOperation elvisExpression infixFunctionCall rangeExpression additiveExpression multiplicativeExpression asExpression prefixUnaryExpression unaryPrefix prefixUnaryOperator excl EXCL NO WS gt gt gt lt lt lt DEFAULT TOKEN CHANNEL postfixUnaryExpression primaryExpression simpleIdentifier Identifier gt gt gt e lt lt lt DEFAULT TOKEN CHANNEL semis NL gt gt gt n lt lt lt DEFAULT TOKEN CHANNEL RCURL gt gt gt lt lt lt DEFAULT TOKEN CHANNEL ```

Klitos Kyriacou · Answer

What s an easy way of remembering the `||` vs ` amp amp ` precedence For me I treat them like `+` and ` ` We all know the precedence of those arithmetic operators since junior school If you treat booleans as numbers with 0 being false and non zero being true as is the case with C then `||` is like `+` true or false = 1 + 0 = 1 = true ` amp amp ` is like ` ` true and false = 1 0 = 0 = false

ephemient · Answer

strictly speaking `||` is saturating add which doesn t have an operator while wrapping add `+` is `xor` but that s the right analogy in general

ephemient · Answer

also note that the infix functions `and` `or` `xor` etc do not have separate precedence from each other because of how infix functions work in Kotlin but you should very rarely if ever see those used on `Boolean`