We should at least have a rules stating "pay attentino you use an
optimised selector". Im not sure what should be form of the warning but
we should make progress
I see two cases
- the dev uses a non optimized version and the warning tell him
that it would be better to use the optimised
ifNil....of whatever case
- when defining a method with such selector:
warn them because we should avoid them.
Stef
Le 1/5/15 10:15, Marcus Denker a écrit :
On 01 May 2015, at 10:08, stepharo <[email protected]> wrote:
Marcus we who
uld add a rule for the or: [b]
Not possible as it is correct if the receiver is a boolean.
Marcus
