Hmm, so that works when I annotate my test class, but I probably shouldn't be
exporting pragma concerns to my end users. Was your other suggestion about
dealing with the warning itself something I could do, or were you referring
to a change to pharo itself?
I think we should remove the warning.
But this just solves the problem for the case where the block for and: has an argument.
When you send and: [] to a non-boolean (your own Boolean), it will nevertheless optimize the contruct���
(but then the #museBeBoolean: magic should take care of it? I think, yes.