Brian S. Julin via RT wrote:
> it would be OK for there to be some tiny chance
>of a collision between two WHICH.Str's as long as the actual WHICHs
>do not collide.
One could make that distinction, but then the .Str of the .WHICH would
not fulfill the purposes for which .WHICH
Brian S. Julin via RT wrote:
> it would be OK for there to be some tiny chance
>of a collision between two WHICH.Str's as long as the actual WHICHs
>do not collide.
One could make that distinction, but then the .Str of the .WHICH would
not fulfill the purposes for which .WHICH
On Wed, 30 Aug 2017 07:03:10 -0700, zef...@fysh.org wrote:
> Brian S. Julin via RT wrote:
> >For example "Foo^".."Bar" and "Foo"^.."Bar" would put out the same WHICH.
>
> Yes, and that's a bigger problem. In general Rakudo's .WHICH methods
> suffer this sort of problem when incorporating the
Brian S. Julin via RT wrote:
>For example "Foo^".."Bar" and "Foo"^.."Bar" would put out the same WHICH.
Yes, and that's a bigger problem. In general Rakudo's .WHICH methods
suffer this sort of problem when incorporating the .WHICH values of
subobjects. See [perl #128943] (Set, and in which I
On Sat, 20 Aug 2016 10:24:51 -0700, zef...@fysh.org wrote:
> > (:a..:b).WHICH
> Range|a True..b True
> > (List..Pair).WHICH
> Use of uninitialized value $!min of type List in string context.
> Methods .^name, .perl, .gist, or .say can be used to stringify it to
> something meaningful. in block
# New Ticket Created by Zefram
# Please include the string: [perl #129019]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129019 >
> (:a..:b).WHICH
Range|a True..b True
> (List..Pair).WHICH
Use of uninitialized value $!min of
