'and' not getting precedence over 'or'

[nevdelap]

class P

	def main is shared
		assert true or (false and false) # Ok
		assert true or false and false   # Barf!

[hopscc]

'and' and 'or' actually have the same precedence and as binary ops they bind to their immediate left and right ( of-less-or-equal precedence) operands so the above is same as

assert (true or false) and false

[nevdelap]

Replying to hopscc:

'and' and 'or' actually have the same precedence and as binary ops they bind to their immediate left and right ( of-less-or-equal precedence) operands so the above is same as
{{{
assert (true or false) and false
}}}

Yes indeed. I misworded.

I should have said and doesn't have precedence over or, which of course it should.

The same is the bug and

assert true or false and false

should be evaluated the same as

assert true or (false and false)

[Chuck]

This was intentional rather than accidental. I don't see that adding another operator precedence level is advantageous, or that you wouldn't want the parens for added clarity. I'll close this ticket unless I'm convinced otherwise.

[nevdelap]

It's not going to matter, but for posterity, 'implies' should have a lower precedence than 'or'.