Issue #19545 has been updated by hurricup (Alexandr Evstigneev). You are explaining from ruby developer perspective and it all makes sense. But from pure language user this feels really strange and inconsistent. Especially `puts((...))` :D `false or not false` is pretty valid expression. And any expression is a valid argument for any call. The only thing that should be in effect there is precedence of ops, commas and parentheses. This is totally non-critical thing, just for the information. Thanks for your time. ---------------------------------------- Feature #19545: lp/hp logic parsing inconsistency https://bugs.ruby-lang.org/issues/19545#change-102635 * Author: hurricup (Alexandr Evstigneev) * Status: Open * Priority: Normal ---------------------------------------- As far as i get it, low precedence logic should behave the same as high precedence. But: This is ok: ``` puts(false || !false) ``` And this is not: ``` puts(false or not false) ``` Feels like in latter case there is some mess with comma precedence. -- https://bugs.ruby-lang.org/