The difference is between the result of "Nil.c" and "Any.c".
On my current version of Rakudo, "Nil.c" returns Nil, while Any.c throws the "No such method" exception. In fact, Nil.any_non_existent method always seems to return Nil. I'm not sure where this is documented, but it's likely the reason you don't get an error with "a.b.c". In your example code, "a.b" returns Nil, so "a.b.c" invokes "Nil.c" which results in Nil and no error. However, assigning Nil to a scalar reverts it to the type otject -- in this case Any. Thus with my $b = a.b; the Nil value coming from "a.b" causes $b to revert to its type object (Any). Then "$b.c" is the same as "(Any).c", which results in the "No such method" exception. See the docs at https://docs.raku.org/type/Nil , in the section that talks about what happens when Nil is assigned to a container. Hope this helps, Pm On Tue, Dec 01, 2020 at 08:34:31AM +0100, Konrad Bucheli via perl6-users wrote: > Hi > > I miss an error on my first invocation of `c` below: > > $ raku > Welcome to 𝐑𝐚𝐤𝐮𝐝𝐨™ v2020.10. > Implementing the 𝐑𝐚𝐤𝐮™ programming language v6.d. > Built on MoarVM version 2020.10. > > To exit type 'exit' or '^D' > > class a { method b {return}} > (a) > > say a.b.c > Nil > > my $b = a.b > (Any) > > say $b.c > No such method 'c' for invocant of type 'Any' > in block <unit> at <unknown file> line 1 > > > > > Is there an explanation for that behavior? > > Cheers > > Konrad >
