On 10 Jan 2015, at 12:20, Evan Donahue <emdonahu@gmail.com> wrote:
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. https://pharo.fogbugz.com/f/cases/14701/compile-normal-message-send-for-and-... <https://pharo.fogbugz.com/f/cases/14701/compile-normal-message-send-for-and-...> 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.
In case it's relevant, the warning also seems to cause an issue where I can't deselect a new class in the system browser and have to re-open the browser.
Thanks, Evan
-- View this message in context: http://forum.world.st/issue-with-and-or-inlining-tp4798622p4798769.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.