> On 9 Jul 2025, at 21:37, Daniel Slomovits <[email protected]> wrote:
>
> This is very cool to see. One note—I would personally not outright deprecate
> #receiver, but leave a comment indicating that it is not guaranteed to be set
> and why. There are plenty of cases where getting nil as the receiver of a
> clean block is correct, or at least good enough—I wouldn't want to eventually
> lose the ability to officially access it entirely, which is what deprecation
> implies.
Yes, true… I wonder how to provide support for people to find potential
problematic use.
One thing we really need is Code Critics, but not doing static analysis but
working on test run data.
We could
-> add probe in #receiver
-> run tests
-> log all send sites
-> tool shows all uses of #receiver that need to be checked
Marcus
