Hi, On Fri, Jan 27, 2017 at 4:09 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Hi Tudor.
2017-01-27 10:23 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Is there a rationale why `self` in instance view does not raise an error or is nil?
That is because you can write: self new and work with an instance.
I expect from you some exciting ideas in this direction. :) Because your examples framework provide many interesting possibility to work always in context of some live instance.
In browser we can add some pluggability to specify what instance use for playing in context of selected class or method. By default it could be just "self new".
Yes, I had ideas along these lines as well. There could be a field above the code panel that defines self as self new, which could be changed accordingly..
It will gives many interesting options: - when "examplar" method is selected "self" will point to describing instance. - when browser is opened from debugger or inspector "self" will point to current object from these tools. - type hints. No type inference - just live information - LightTable features. When method is selected, it executed in background and browser collects and show live data: temp types, values, execution could, dead code, also visualization if possible.
So it could add many power to our environment.
-- Siemen