Re: [Pharo-dev] Rationale behind the "ifTrue:/ifFalse: returns instead of and:/or:'s" rule

[Denis Kudriashov]

2017-04-07 11:23 GMT+02:00 marcus.den...@inrira.fr <marcus.den...@inria.fr>:

> I really do not like the complex boolean expressions… my brain can
> understand the “check and return” guards extremely fast:
>
>                 backgroundColor ifNil: [ ^ true ].
>                 (backgroundColor isColor and: [ backgroundColor
> isTranslucentButNotTransparent ]) ifTrue: [ ^ true ].
>                 (borderColor isColor and: [ borderColor
> isTranslucentButNotTransparent ]) ifTrue: [ ^ true ].
>                 ^ false
>
> while for the nesting everything in one huge or: /and: expression I have
> to think. I always feel that replacing the “guard”
> style with complex nested booleans makes the code worse.
>
> I really would like to remove the rule.
>

Me too