So is the current behavior good or bad?
On 2014-10-15 05:16:27, barto...@gmx.de wrote:
> The current behaviour is:
>
> $ perl6-m -e 'my %h{Any}; %h=Any; %h //= "a"; say %h.perl'
> Hash[Any,Any].new("a" => "a")
>
> $ perl6-m -e 'my %h{Any}; %h //= "a"; say %h.perl'
> Hash[Any,Any].new("a" => "a")
>
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #118023]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org:443/rt3/Ticket/Display.html?id=118023 >
r: https://gist.github.com/lizmat/5594924
rakudo 570d1d: OUTPUT«("Foo::Bar" =>
The folks at O'Reilly have handed me 20 discount slots for OSCON this
year for "Parrot core contributors", whatever that's supposed to
mean. These are 15% off the registration cost, and can be used with
other discounts. (There's an early-bird 20% discount if you regis
essing the value, as the next
Apocalypse will make clear.)
: (And if Damian's
: happy with slots, that probably means we can get a lot of the other
: attribute recipies out of the way pretty quick. Huzzah!)
:
: I had mixed feelings about defining and using a term like "slots" in a
Thanks, if it's looking like lvalues are really out I'll edit that draft
to take out the lvalue stuff and do it the other way. (And if Damian's
happy with slots, that probably means we can get a lot of the other
attribute recipies out of the way pretty quick. Huzzah!)
I had
This all looks good to me. I seem to have gone off on a tangent about
slots, so I've mercifally changed the subject.
On Fri, Oct 04, 2002 at 04:39:40PM -0700, Michael Lazzaro wrote:
> [CONS]
>
> - Making publicly accessible attributes at all is considered Bad Form
> in most
I had imagined the way things like
$R = 0 but true
would work is that the scalar would grow another couple of slots
in it, which would be the conversion operators. Everything defaults
to how it has worked in the past, but could be overridden. So the
boolean value starts as "de
