view release on metacpan or  search on metacpan

t/lib/Hailo/Test/TimToady.trn  view on Meta::CPAN

so I'd be happy if it made a noise like a hoop and rolled away
so there!
you have to put ; after the {}
if it's on the same line
std: class A {} class B { has %.foo{A} }
std: class A {}; class B { has %.foo{A} }
(I don't think rakudo supports [] or {} on declarations yet, though)
perl6: say ~[\*] 1..10
n
like .repr in python, except we think there's more than one possible representation :)
it is not guaranteed :)
or we'd have to write test cases for python, ruby, lisp, bf, tcl, etc.  :)
why do you need the indirection?
why did the module need the indirection?
short answer is using Captures
which S08 will theoretically be about
but basically you're talking about a list of one element, one way or another
some container that happens to hold only one element
you can do it with a Capture, but it's different from P5 in that it automatically derefs it for you
the most general container may end up being something called a Parcel though
hasn't hit the spec yet though
and, of course, you can always define an object that contains a single attribute
you can blame the persistence of Juerd++ for <->
in case there are two arrays
std: @a >>* 2
yeah, parsed it as @a > >
std: @a >> 42
hmm
std: @a >>42
curious
std: @a >>|| 42
something like that
but it ought to have reset the high-water mark somewhere
there are still times when it really ought to just say "I'm really confused here"
greetin's
not currently
at the moment you'd declare your variables with 'int' type to do something similar
a little harder, but less likely to get you into accidental trouble
the second is wrong
Wiley Codey
not yet
finanalyst: traits mix in methods to an object at compile time, so once the variable is declared, it's introspection is like the introspection of any other object, and "I came from a trait" is not known.
*its
rakudo: my @x is readonly; say @x.readonly
std: asdf
zzz &
consecutively
you can tell it to operate in parallel however, if the 'for' is in hyper context
my @result = hyper for < 1 2 3 > -> $number { do_something($number) }
that tells the for it can run them in parallel
currently specced, but I'm sure not implemented
is do_something not idempotent?
should be doing them sequentially
possibly a scoping problem?
so you're starting over somehow?
how does the second iteration learn of the first iteration's results?
what is your board stored in?
declared where and how?
how is the board declared, in in what scope?
which declarator are you using?
you might print out .WHICH on the two iterations to see if you're really modifying the same object
with 'has', I presume
if you're sure you're dealing with the same Board each time through, then the problem would be on the setting and sticking end, I suppose
I doubt that rakudo would be trying to do any concurrency
asciiville: a class name has to be predeclared before you can use it, but you can put class Foo {...} with the ... stub
that would serve as a forward declaration
alternately, you can say ::Foo for a not-yet-defined ref
(though not in a declarative context, alas)
we should probably separate those concepts...
but currently, if you need sub foo (::Foo $bar) you have to use class Foo {...} instead
since the ::Foo would mean to capture the type of the $bar parameter en passant
rakudo probably needs "is also" on the real definition to suppress warnings
and "is also" will change to "augment" in rakudo someday
but you shouldn't need either if the original was a stub
== is numeric
jaldhar++ for making progress
@karma jaldhar
jaldhar++ for having the courage to ask questions too
@karma jaldhar
the == ought to have been giving you warnings, I think
but perhaps not, depending on if we think '' is a valid representation of 0
maybe it's something the compiler could notice
ENOKLOO # not a PIR expert
ah yes, one of the many SWA "hubs" :)
always fun landing over the hill in SD
oh, were you in the new terminal B?
peddle hard
as a statement separator, it's a very good spot to figure out that someone didn't terminate their regex properly
and it was already an "unrecognized metacharacter"
this just let's us give a more useful message in the case that they actually did leave off the terminator
*lets
I can probably give a better message for /;/ though
I take it the ${$var} is done by something else, because it's certainly no legal Perl 6
*not
and to switch to a syntax where you could add modifiers easily
such as to determine what will or will not interpolate
that's already handled by default in p6
since @example won't interpolate without a [] afte rit
after it
it's really the sum total of lots of little killer features that adds up
it's becoming more of a priority as time goes on
but hasn't been till now
you'll have to be very careful then, because hacking on this stuff is highly addictive
you could use the webpage apparatus that was built for pugs
see the smoke target in pugs/Makefile
assuming you have the pugs repo handy
that's also where we store all the spec tests
so if you want to whack on those, a commit bit is very easy to acquire
all the specs are in the pugs repo as well
if you want a pugs commit bit, we can get you one in about a minute
oh, where's your sense of adventure :P
oops
as far as I know, I don't have an invite yet
you already have it
std: :$^bar
std: :$*bar
unless you declare ($self:)
hoelzro: do you have a pugs commit bit?
do you still have a repo image?
I can resend the commit bit if you've forgotten your password
looks like KyleHa++ tweaked it some