Is it okay that the Playground's inspector drills down on the self
variable indefinitely?

It is... #(1 2 3) "Do it and go" will result in an Array being
inspected, if I click on "self" it will open a new inspector on the
side on the same object, and this can as deep as you want.

I would block that from happening, in the raw tab, the "self" variable
shouldn't drill down, sometimes I just want to select it to run an
expression where self refers to the inspected object.

Does it make sense what I propose? Or is there any use case where
drilling down recursively ad infinutum is useful?


Regards!

Esteban A. Maringolo

Reply via email to