On 12 Jan 2015, at 12:08, Marcus Denker <marcus.denker@inria.fr> wrote:
On 12 Jan 2015, at 10:57, Marcus Denker <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
On 10 Jan 2015, at 12:20, Evan Donahue <emdonahu@gmail.com <mailto: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-...>
This is now in Pharo4 update 40439
I made another change that removes the checks from all but âifâ inlining: https://pharo.fogbugz.com/f/cases/14716/Remove-all-notify-from-inline-checki... <https://pharo.fogbugz.com/f/cases/14716/Remove-all-notify-from-inline-checki...> maybe we should even remove it from ifTrue*⦠there is checks that the blogs have 0 args. (if we remove it it will instead compile a message send and then raise the error at runtime, making ifTrue&co optimisation transparent, too. Marcus