New debugging tools are all adding singletons about newtools HOT 4 OPEN

Can you elaborate a bit more?

from newtools.

Each time we add a debugging tool, there is a class with a singleton that holds objects.
For example, the halt cache uses a registry of halts, the debugger selector keeps instances of DebugSession, the object-centric debugger keeps instances of object-centric breakpoints, etc.

Basically all the (debugging) tools need to keep instances of things somewhere and control them from there.

We are constantly adding singletons, with different namings (defaultInstance, default, singleton, etc.), then testing them (globally the same way).

Why not having a "Singleton service" that proposes an interface for "Singleton clients" that would be able to register their objects there?

from newtools.

Yes, one tiny step: There was the proposal to add a Stateful trait for Singletons.

• Konrad implemented it and changed all singletons, but it was rejected as a (undefined) part of that is not supposed to use Tratis
• I re-submitted the trait only so people can start to use it, but that was rejected as it had no users.

see pharo-project/pharo#3204

from newtools.

I understood @StevenCostiou 's point as to avoid singletons, not making them just easier to use. Singletons are in general not a good solution as they prevent testing, isolating changes...

from newtools.