Skip Menu |
Report information
Id: 126113
Status: open
Priority: 0/
Queue: perl6

Owner: Nobody
Requestors: FROGGS.de <email [at] froggs.de>
Cc:
AdminCc:

Severity: (no value)
Tag: (no value)
Platform: (no value)
Patch Status: (no value)
VM: (no value)



Subject: [BUG] Cannot bind to &::("CORE")::foo
To: rakudobug [...] perl.org
From: Tobias Leich <email [...] froggs.de>
Date: Sun, 20 Sep 2015 09:55:31 +0200
Download (untitled) / with headers
text/plain 153b
t/spec/S02-names/pseudo.t expects that you can do: use Test; plan 1; sub f3() { } &::("CORE")::none := &f3; ok &none =:= &f3, 'works';
Subject: Re: [perl #126113] [BUG] Cannot bind to &::("CORE")::foo
To: perl6-compiler [...] perl.org
Date: Sun, 20 Sep 2015 15:58:31 +0200
From: Moritz Lenz <moritz [...] faui2k3.org>
Download (untitled) / with headers
text/plain 580b
On 09/20/2015 09:55 AM, Tobias Leich (via RT) wrote: Show quoted text
> # New Ticket Created by Tobias Leich > # Please include the string: [perl #126113] > # in the subject line of all future correspondence about this issue. > # <URL: https://rt.perl.org/Ticket/Display.html?id=126113 > > > > t/spec/S02-names/pseudo.t expects that you can do: > > use Test; plan 1; > sub f3() { } > &::("CORE")::none := &f3; > ok &none =:= &f3, 'works';
I'm pretty sure that test is incorrect. Lexical scopes are read-only after compile time, and &::CORE is a lexical scope, after all.
Subject: [BUG] Cannot bind to &::("CORE")::foo (Or bogus test?)
Download (untitled) / with headers
text/plain 473b
Yeah, the test (as well as the surrounding ones that do pass) seems fishy. I also don't see the tested behavior described in S02. The only example code in S02 that shows binding to a `&` LHS is this: my &func := sub { say "Hi" }; ...which declares a new symbol in the current scope, rather than modifying an already closed scope. (I'll abuse the `testneeded` tag again, to mean "Needs someone experienced with Roast to investigate and potentially fix/remove test.")


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org