On Mon, 23 Jan 2017 01:37:16 -0800, alex.jakime...@gmail.com wrote:
> Code:
> class C { method defined { True } }; say ?C
>
> Result (2015.12,2016.02):
> True
>
> Result (2016.03,HEAD):
> False
>
>
>
> Bisectable points to
> https://github.com/rakudo/rakudo/commit/24b4b23a80337888cf5ea47b091d218bc884d682
>
> The commit message did not indicate that “defined” method should no
> longer work, so my best guess is that the change is not intentional.
>
> However, if this is not supposed to work, then what about throwing an
> error when the user attempts to create a “defined” method?
+1 to smsl's and lizmat's response (on mailing list).
Custom `defined` method still works; the Bool method—which is what your
operator calls—simply got decoupled from it.
The new behaviour is less surprising: only what the user actually overrides is
affected. And I agree with lizmat that is isn't a bug.
