Hi Christoph,

I don't want to keep you from contributing to Squeak, but I'm not sure
if adding convenience methods like this is a good idea. Why? I have
lots of such methods myself (some of them I even got from others). But
as long as they have no senders/purpose in the image, it pretty much
just means:

a) they are hard to discover and to keep up-to-date,
b) everyone has to maintain everyone's convenience methods (e.g in
case Context>>#runSimulated ever changes),
and c) at some point, we may have users relying on (the wrong) API
which should not be used in production.

I have a set of personal packages in which I keep things like this.
What do you think?

Fabio

On Sun, Mar 22, 2020 at 8:25 PM <commits at source.squeak.org> wrote:
>
> A new version of Kernel was added to project The Inbox:
> http://source.squeak.org/inbox/Kernel-ct.1320.mcz
>
> ==================== Summary ====================
>
> Name: Kernel-ct.1320
> Author: ct
> Time: 22 March 2020, 8:25:11.31556 pm
> UUID: d08c3179-cda9-2944-b692-9ef1b00d7742
> Ancestors: Kernel-eem.1319
>
> Proposal: Add convenience method #runSimulated to BlockClosure. While this should not be used in production, it can be helpful for exploring and testing the simulation machinery.
>
> =============== Diff against Kernel-eem.1319 ===============
>
> Item was added:
> + ----- Method: BlockClosure>>runSimulated (in category 'system simulation') -----
> + runSimulated
> +
> +       ^ Context runSimulated: self!
>
>