On 30 May 2017 at 12:46, Alidra Abdelghani via Pharo-users < pharo-users@lists.pharo.org> wrote:

I did not knew about that one :) Still, it is too bad that we have this constraint, because it is very difficult to find the problem if you dont know about this rule already (especially for newbies). Hopefully, this is going to be fixed in the future.

It sure looks like a good candidate for a framework-specific critic rule…