> On 17 Mar 2022, at 18:00, Esteban Maringolo <emaring...@gmail.com> wrote:
>
> That is great!
>
> Is it possible to disable it for doits and other playground expressions?
>
No, there is no hook yet… it would be interesting to see how to do that.
(e.g. per playground compiler parameters, parameters for doit independent of
the compiler used for compiling methods…)
What you can do is turning it off globally in the setting (all compiler option
are listed there)
But take care: we can not recompile the image without optimzations as this adds
intererrupt possibilities to code that was not
interruptable before, which breaks the code in for process switching itself, I
think.
> Regards!
>
> Esteban A. Maringolo
>
> On Thu, Mar 17, 2022 at 1:23 PM Marcus Denker <marcus.den...@inria.fr> wrote:
>> On 17 Mar 2022, at 17:17, Richard Sargent
>> <richard.sarg...@gemtalksystems.com> wrote:
>> A pragma might be the way to go.
>> <noInline: #and:> for example.
>>
>>
>>
>> There is already the #compilerOptions: Pragma, e.g.:
>>
>> <compilerOptions: #(- optionInlineAndOr )>
>> For example this method compiled the and: as a real send:
>> tt
>> <compilerOptions: #(- optionInlineAndOr)>
>> true and: [ false ]
>>
>>
>> On Thu, Mar 17, 2022 at 8:17 AM Esteban Maringolo <emaring...@gmail.com>
>> wrote:
>
>>> A great trade off would be to be able
>>> to enable/disable for certain things instead of it being a global
>>> setting.
