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

1) it’s not only about removing. Maybe we should detect complicated boolean expressions that return something and suggest to break them down.

No idea…

2) I just want to know why someone created such rule :). Because the author of the last update of the initialize method is Marcus :)

I did not add it originally. Marcus