This now works on the JVM backend, too. Fixed with
https://github.com/rakudo/rakudo/commit/12d4514a3d
I'm closing this ticket as 'resolved'.
This is still a problem on the JVM backend. I tried a second time to find the
underlying problem and arrived at the same conclusion: There seems to be
something wrong in 'analyze_dispatch'. When running the given code
multi foo ($) {"right" }; multi foo ($ is rw) {"wrong"}; say foo "42"
I suggest check out below links:
https://github.com/mickael-kerjean/filestash/issues/61
https://github.com/termux/termux-packages/issues/307
Good luck,
On Mon, 29 Jan 2018 13:24:45 -0800, myforumem...@arcor.de wrote:
> Device: Onyx Boox Max2, Android 6.0.1, cpu rk3288
> termux is a prefixed
Using spaces in prefix path should work now. There was some serious revamp of
the build system during the last couple of months. I didn't have all the
details, but some relevant pull requests for Rakudo have probably been:
* https://github.com/rakudo/rakudo/pull/2693
*
On Sun, 31 Jul 2016 19:14:19 -0700, c...@zoffix.com wrote:
> Can't reproduce the issue.
>
> Are you able to try again with the latest Rakudo, please?
Since there was no update on this ticket, I'm closing (rejecting) it now. I'm
pretty sure we'd have more bug reports if this would be an issue
Back in 2017 jnthn++ already added a test for lazy for loops with
https://github.com/perl6/roast/commit/3659ede149. Since the evaluations in this
ticket also take the type into considerations, I've added a new test to
S32-list/seq.t with https://github.com/perl6/roast/commit/207171b5ee
I'm
I've added a test to S02-names/pseudo-6e.t with
https://github.com/perl6/roast/commit/73d867501c
I'm closing this ticket as 'resolved'.
The skip directive has been removed (at least for v6.e) with commit
https://github.com/perl6/roast/commit/04c7d09341 (see also
https://github.com/perl6/roast/commit/2913fbe564 for v6.c and v6.d).
I'm closing this ticket as 'rejected', since there wasn't added any additional
information.
These tests have been adjusted with
https://github.com/perl6/roast/commit/551a7ffd7b
I'm closing this ticket as 'resolved'.
This test works with more recent Java version, cmp.
https://github.com/perl6/roast/commit/b5c4ed2345
I'm closing this ticket as 'resolved'.
This test works now, cmp. https://github.com/perl6/roast/commit/472bc003f0
I'm closing this ticket as 'resolved'.
The test in question works now, cmp.
https://github.com/perl6/roast/commit/bba5083af5.
I'm closing this ticket as 'resolved'.
Test has been removed with https://github.com/perl6/roast/commit/1a88ef7e03.
I'm closing this ticket as 'rejected'.
Test has been removed with https://github.com/perl6/roast/commit/1a88ef7e03.
I'm closing this ticket as 'rejected'.
Test has been removed with https://github.com/perl6/roast/commit/1a88ef7e03.
I'm closing this ticket as 'rejected'.
Test has been removed with https://github.com/perl6/roast/commit/1a88ef7e03.
I'm closing this ticket as 'rejected'.
On Thu, 21 Jul 2016 19:43:35 -0700, c...@zoffix.com wrote:
> Still present in Rakudo version 2016.07.1-28-gd789da1 built on MoarVM
> version 2016.07-3-gc01472d
>
> Interestingly, this doesn't happen on camelia running the same commit.
>
> zoffix@VirtualBox:~/CPANPRC/rakudo$ ./perl6-m -e 'BEGIN {
450351791.17598 '')
> in block at -e:1
>
> and that if you replace the () with 'do' it doesn't happen.
>
> On Thu, Dec 17, 2015 at 10:35 PM perl6 via RT
> wrote:
>
> > Greetings,
> >
> > This message has been automatically generated in response to the
> > crea
On Mon, 13 May 2019 10:28:25 -0700, jan-olof.hen...@bredband.net wrote:
> On Thu, 29 Dec 2016 13:26:17 -0800, alex.jakime...@gmail.com wrote:
> > Code:
> > say Hash[Int].new(‘abc’ => 20..50)
> >
> >
> > Result (2015.12):
> > Type check failed in binding $x; expected Int but got Range
> > in
On Thu, 29 Dec 2016 13:26:17 -0800, alex.jakime...@gmail.com wrote:
> Code:
> say Hash[Int].new(‘abc’ => 20..50)
>
>
> Result (2015.12):
> Type check failed in binding $x; expected Int but got Range
> in block at /tmp/CRJOhWZaTS line 1
> «exit code = 1»
>
>
> Result (HEAD):
> {abc =>
On Sun, 02 Apr 2017 07:48:11 -0700, alex.jakime...@gmail.com wrote:
> I wonder, is it a dup of RT #124553 and RT #125353 ?
>
> On 2017-04-02 04:50:15, c...@zoffix.com wrote:
> > If joined colonpairs are after a position arg, only the first
> > colonpair gets registered:
> >
> > m: -> *@_, *%_ {
On Thu, 04 May 2017 17:36:32 -0700, c...@zoffix.com wrote:
> On Thu, 10 Nov 2016 21:03:43 -0800, joshu...@gmail.com wrote:
> > Normally Rakudo is happy for you to omit comma when declaring pairs
> > with
> > the `:key(value)` syntax, however I found that it does not like this
> > syntax
> > is
On Sun, 12 May 2019 07:36:16 -0700, jan-olof.hen...@bredband.net wrote:
> On Sat, 26 Aug 2017 05:15:41 -0700, sml...@gmail.com wrote:
> > This bug is still present in
> >
> > Rakudo version 2017.08-8-g753c9a5ea built on MoarVM version
> > 2017.08.1-
> > 19-g151a2563
> > implementing Perl 6.c
>
>
On Sat, 26 Aug 2017 05:15:41 -0700, sml...@gmail.com wrote:
> This bug is still present in
>
> Rakudo version 2017.08-8-g753c9a5ea built on MoarVM version 2017.08.1-
> 19-g151a2563
> implementing Perl 6.c
As per commit
On Sat, 30 Sep 2017 12:40:59 -0700, sml...@gmail.com wrote:
> On Mon, 29 May 2017 11:36:49 -0700, c...@zoffix.com wrote:
> > On Mon, 29 May 2017 10:02:27 -0700, thunderg...@comcast.net wrote:
> > > Using a cross meta operator on an empty list complains "This type
> > > (Scalar) does not support
On Fri, 15 Dec 2017 01:18:46 -0800, d...@zwell.net wrote:
> The output of a hash of hashes of ints looks my Hash[Int] %nested-
> type;
> %nested-type.WHAT.say; # output: (Hash[Hash)
>
> The type should be shown as: (Hash[Hash[Int]])
>
> AlexDaniel did a bisect and found this was caused by:
>
On Tue, 21 Feb 2017 11:05:15 -0800, c...@zoffix.com wrote:
> On Sun, 01 May 2016 04:12:34 -0700, alex.jakime...@gmail.com wrote:
> > This bug report is somewhat related to
> > https://rt.perl.org/Ticket/Display.html?id=128046
> >
> > get() crashes with a weird error if the stream has ended.
> >
>
On Sun, 04 Feb 2018 02:40:44 -0800, alex.jakime...@gmail.com wrote:
> Actually, I've been trying to reproduce it on the said revision with
> --profile,
> --ll-exception and whatnot, and I can't. I think this is an issue on
> OS X and
> therefore should be confirmed (and tested) on OS X also.
>
>
Can confirm this is still current behaviour with Rakudo 2019. I have came
across exactly the same issue and found this ticket. I've noticed, If I change
the example to catch exceptions. It then runs:
sub start-element($, $elem, $attr)
{
say "open $elem".indent($depth * 4);
Le Fri, 26 Apr 2019 08:28:23 -0700, n...@detonation.org a écrit :
> I'm quite sure all the issues in that ticket have been resolved.
Yes. We managed to create separate Debian packages for moar, nqp and rakudo. We
are also creating package for individual Perl6 modules, but we're still for
from
I have committed https://github.com/perl6/nqp/commit/59d7a8869c and this test
passes now.
As far as I understand, the right handler was missed when moving to the
outside, because unwind_check sets the outer handler to 0 by default if no
outer handler is passed. We do the latter now.
I'm
As jmerelo++ pointed out [1] the statement prefix 'lazy' has been fixed back in
2015 with https://github.com/rakudo/rakudo/commit/d043961414. It no longer
shares the implementation with 'do'.
The tests that are fudged with this ticket don't work, though. The test file
S04-statements/lazy.t is
On Thu, 04 Apr 2019 22:59:38 -0700, barto...@gmx.de wrote:
> I'm going to unfudge the test in S02-magicals/sub.t for rakudo.jvm.
For the record: https://github.com/perl6/roast/commit/aaf7ad02fc
On Thu, 04 Apr 2019 23:09:43 -0700, barto...@gmx.de wrote:
> I'm going to unfudge the test in S32-str/length.t and close this ticket.
For the record: https://github.com/perl6/roast/commit/aaf7ad02fc
On Thu, 04 Apr 2019 23:15:25 -0700, barto...@gmx.de wrote:
> I'm going to change two skipped tests to 'todo'.
For the record: https://github.com/perl6/roast/commit/aaf7ad02fc
Just for the record: This seems to work on the JVM backend:
$ ./perl6-j --optimize=3 -e 'sub f() { sub g() { if True { return
&?ROUTINE.name } } }; say f()()'
g
I'm going to unfudge the test in S02-magicals/sub.t for rakudo.jvm.
As a result for https://github.com/rakudo/rakudo/issues/2764 with fix in
https://github.com/rakudo/rakudo/commit/c9110654bd5e9dffc163627f13b896b25dff0679
I think this can be closed.
The problem is the PEM_write_bio_RSAPrivateKey signature used in the NativeCall
declaration, it missed five arguments.
>From the manual:
int PEM_write_bio_RSAPrivateKey(BIO *bp, RSA *x, const EVP_CIPHER *enc,
unsigned char *kstr, int klen,
OK, so that's not an issue in Rakudo then. Closed.
On 2019-03-05 11:16:41, sortiz wrote:
> The problem is the PEM_write_bio_RSAPrivateKey signature used in the
> NativeCall declaration, it missed five arguments.
>
> From the manual:
>
> int PEM_write_bio_RSAPrivateKey(BIO *bp, RSA *x, const
Moved to https://github.com/rakudo/rakudo/issues/2725
On 2016-12-29 14:43:03, alex.jakime...@gmail.com wrote:
> Of course, same thing with “next” and “last” (is there anything else?)
>
> On 2016-12-29 09:13:24, alex.jakime...@gmail.com wrote:
> > Code:
> > say 42; redo
> >
> >
> > Result
Closing, explanation here: https://github.com/rakudo/rakudo/issues/2708
On 2017-05-12 07:52:34, c...@zoffix.com wrote:
> https://irclog.perlgeek.de/perl6-dev/2017-05-12#i_14572067
>
> 14:49 m: my @a = 1..12; for ('a' x 100 ~ " -- Jan-12-2017")
> xx 100 { when /'-- ' |@a '-' \d**2 '-' \d**4 / { }
Ticket moved to https://github.com/rakudo/rakudo/issues/2697
On 2015-09-25 14:06:27, duff wrote:
> On Sat Jul 25 12:03:18 2015, moritz wrote:
> > This script here:
> >
> > # BEGIN SCRIPT
> > my grammar PgTokenizer {
> > token double_quote_normal { <-[\\"]>+ }
> > token double_quote_escape { [\\ .
.
"Concentrationism"
On 1/25/19 1:20 PM, Aleks-Daniel Jakimenko-Aleksejev via RT wrote:
> Usually this happens when you have an unclosed string somewhere earlier in
> your
> code.
>
> That is:
>
> say "foo; ← oops! Forgot the closing "
>
> # $a ← we think
Oh, for me I just moved on to a proper bit of code.
I filed the bug for the perfection of the parser so
it's less exploitable. :)
"I code therefore I am!"
On 1/26/19 8:17 PM, Timo Paulssen via RT wrote:
> I believe the problem comes from `"{"` which actually starts an
&g
"JSON") ~ " else " ~ (say "NOTJSON") ~ ";
# my %bb = 1234 => 99;
again no closing double-quotes
Does that help?
On 25/01/2019 07:20, Aleks-Daniel Jakimenko-Aleksejev via RT wrote:
> Usually this happens when you have an unclosed string somewher
Usually this happens when you have an unclosed string somewhere earlier in your
code.
That is:
say "foo; ← oops! Forgot the closing "
# $a ← we think that this is a comment, but actually it's part of the string
above!
On 2019-01-23 01:27:08, warren.mu...@gmail.com wrote:
> Hello:
>
> I ran into
I'm slightly confused by this ticket… isn't it resolved now? Nowadays you get
an error message like this:
Unable to parse expression in single quotes; couldn't find final "'"
(corresponding starter was at line 2)
So while it blows up at the end of the file, it still mentions where the quote
# New Ticket Created by Warren W. Music Jr.
# Please include the string: [perl #133791]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133791 >
Hello:
I ran into this while setting up a post test for json
in bailador. While
# New Ticket Created by Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯
# Please include the string: [perl #133772]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133772 >
rpm -qi rakudo | rg Version
Version : 2018.12
my Str $s = 'abc';
my @l
Fixed for Bag/BagHash with https://github.com/rakudo/rakudo/commit/fe38bdba62
Fixed for Mix/MixHash with https://github.com/rakudo/rakudo/commit/bcc8054a4d
> On 13 Jan 2019, at 22:03, Elizabeth Mattijsen via RT
> wrote:
>
> Fixed for Set/SetHash with https://github.com/rakudo/r
Fixed for Set/SetHash with https://github.com/rakudo/rakudo/commit/4bb5c33c72
> On 10 Jan 2019, at 18:22, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 (via RT)
> wrote:
>
> # New Ticket Created by Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯
> # Please include the string: [perl #133762]
> # in the subject line of all future co
# New Ticket Created by Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯
# Please include the string: [perl #133762]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133762 >
› rpm -qi rakudo | rg Version
Version : 2018.12
subset Foo of Str where .chars
Tests in
https://github.com/rakudo/rakudo/blob/bfe2ad63f8ea17cbc11e836b7fcb1c8f35515cbd/t/04-nativecall/18-routine-sig-sanity.t#L95
On Tue, 03 Oct 2017 08:34:39 -0700, c...@zoffix.com wrote:
> If you `use` a v6.d, it causes language switch and will also complain
> if the version is too high.
> The same doesn't happen with `need`. It should probably fail in these
> cases, and `` should
> be just removed from the grammar[^1].
>
On Tue, 03 Oct 2017 08:34:39 -0700, c...@zoffix.com wrote:
> If you `use` a v6.d, it causes language switch and will also complain
> if the version is too high.
> The same doesn't happen with `need`. It should probably fail in these
> cases, and `` should
> be just removed from the grammar[^1].
>
Actually, if you change it to .*| -- this will work as you
expect. It's a bug that your version doesn't work, of course. It does
seem to involve tangentially, but it is unrelated to underscore.
On Mon, Oct 1, 2018 at 6:17 PM Vijayvithal via RT <
perl6-bugs-follo...@perl.org>
. Michaud via RT wrote:
> The issue doesn't seem to be the underscore, because I get the same result
> even when converting the underscore into a letter ('b'):
>
> $ cat gentb.p6
> grammar G0 {
> token TOP {|.*}
> regex rport { }
> rule ruport
example does not.On Sep 28, 2018 8:22 AM, Brandon Allbery
via RT wrote:
>
> "_" is not an alphabetic character. It's allowed in "alnum" because that is
> by intent what is \w in other regex implementations, which includes "_".
>
> On Thu, Sep 27, 2018 at
,
Alnum1.parse($str),
"=== (reversed) ===",
AlnumReversed.parse($str),
"=== ==",
Alpha1.parse($str),
"=== Regex ==",
$str ~~ $rx;
On Fri, Sep 28, 2018 at 7:19 AM Patrick R. Michaud via RT <
perl6-bug
The issue doesn't seem to be the underscore, because I get the same result even
when converting the underscore into a letter ('b'):
$ cat gentb.p6
grammar G0 {
token TOP {|.*}
regex rport { }
rule ruport { }
#token type {+}
token type {+}
}
grammar G1 {
Are you sure about that? Underscore has been part of the specs (synopses)
for for at least 10 years, probably longer.
> "_" ~~ //
｢_｣
alpha => ｢_｣
On Thu, Sep 27, 2018 at 7:52 PM Brandon Allbery wrote:
> "_" is not an alphabetic character. It's allowed in "alnum" because that
> is by
"_" is not an alphabetic character. It's allowed in "alnum" because that is
by intent what is \w in other regex implementations, which includes "_".
On Thu, Sep 27, 2018 at 10:47 PM Vijayvithal
wrote:
> # New Ticket Created by Vijayvithal
> # Please include the string: [perl #133541]
> # in
# New Ticket Created by Vijayvithal
# Please include the string: [perl #133541]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133541 >
In the attached code, the only difference between the Grammars G0 and G1
is the
On Sun, 28 Aug 2016 09:40:51 -0700, barto...@gmx.de wrote:
> Just a note: This seems to be a specific problem with Moar:
>
> $ ./perl6-j
> [...]
> > my int8 $i = 0x78;
> 120
> > my int8 $j = 0x78;
> 120
> >
>
> I'm going to tag this ticket with [MoarVM]. Or should the ticket be
> moved to the
On Sun, 28 Aug 2016 09:40:51 -0700, barto...@gmx.de wrote:
> Just a note: This seems to be a specific problem with Moar:
>
> $ ./perl6-j
> [...]
> > my int8 $i = 0x78;
> 120
> > my int8 $j = 0x78;
> 120
> >
>
> I'm going to tag this ticket with [MoarVM]. Or should the ticket be
> moved to the
> On Tue, 04 Apr 2017 11:05:05 -0700, c...@zoffix.com wrote:
> This is partially fixed now for `is equiv` with
> https://github.com/rakudo/rakudo/commit/f9f0883c6c and
> https://github.com/perl6/roast/commit/75f42755ec
FYI: with 6.d prep going on, I reverted[^1] that test for now
Don't want to
> On Tue, 04 Apr 2017 11:05:05 -0700, c...@zoffix.com wrote:
> This is partially fixed now for `is equiv` with
> https://github.com/rakudo/rakudo/commit/f9f0883c6c and
> https://github.com/perl6/roast/commit/75f42755ec
FYI: with 6.d prep going on, I reverted[^1] that test for now
Don't want to
I patched Gumbo to no longer create an XML tree but just a bunch of hashes, yet
the error remains. So it's clearly not the XML module causing the issue but
some NativeCall Gumbo thing. Gumbo makes heavy use of structs and nested
structs. I guess the latter could be worth having a look as that's
On Mon, 21 Aug 2017 07:38:56 -0700, alex.jakime...@gmail.com wrote:
> It was removed completely for 2017.08 release.
>
> Rakudo commit:
> https://github.com/rakudo/rakudo/commit/465d91abdfda038cb7feda35f7966be4ec39acf3
> Discussion: https://irclog.perlgeek.de/perl6-dev/2017-08-21#i_15048995
> On
, b, c
> On 18 Jul 2018, at 17:32, Alastair Douglas via RT
> wrote:
>
> On Mon, 19 Jun 2017 09:30:41 -0700, brad wrote:
>> The way Moose in Perl 5 works around this is to give it a subroutine
>
>> there currently isn't as far as I know, a way to do what you intended.
>
On Mon, 19 Jun 2017 09:30:41 -0700, brad wrote:
> The way Moose in Perl 5 works around this is to give it a subroutine
> there currently isn't as far as I know, a way to do what you intended.
I'd like this feature as well. I was in IRC asking about whether we could
restrict a hash in the same
Another user opened the same ticket on our primary tracker, so I'll close this
one in favour of that one:https://github.com/rakudo/rakudo/issues/2098
I'm not sure. Probably your idea of warning about detected encoding is better.
S
On Thu, 12 Jul 2018 at 09:58, Kamil Kułaga via RT
wrote:
>
> Will it work fine for utf-16 users?
> On Wed, Jul 11, 2018 at 11:16 AM Steve Mynott via RT
> wrote:
> >
> > Maybe the Windows p
Will it work fine for utf-16 users?
On Wed, Jul 11, 2018 at 11:16 AM Steve Mynott via RT
wrote:
>
> Maybe the Windows port of rakudo should set this automatically on startup?
> On Wed, 11 Jul 2018 at 10:08, Kamil Kułaga via RT
> wrote:
> >
> > I found resolution. It
Maybe the Windows port of rakudo should set this automatically on startup?
On Wed, 11 Jul 2018 at 10:08, Kamil Kułaga via RT
wrote:
>
> I found resolution. It looks like it is problem windows locale issue than
> perl itself.
>
> Running command
>
> chcp utf8
>
> Ma
I found resolution. It looks like it is problem windows locale issue than perl
itself.
Running command
chcp utf8
Makes work just fine. Default is 852. I'm very supprised because I use unicode
encoding all the the time and never had such issue. For me it would be better
to detect if
# New Ticket Created by Brandon Allbery
# Please include the string: [perl #133300]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133300 >
[25 00:11:06] What is wrong with this one:
`&::($RunSpecific)();` No such symbol
On Sun, 04 Sep 2016 11:35:06 -0700, ddgr...@gmail.com wrote:
> When running the below code, using a moar built with --debug
> valgrind --trace-children=yes ~/Source/perl6/install/bin/perl6 -e 'for
> ^1000 { my $proc = run(:out, :bin, ‘tar’, ‘cf’, ‘-’, ‘--absolute-
> names’, ‘--’,
On Tue, 03 Nov 2015 08:54:16 -0800, root+bitc...@retupmoca.com wrote:
> On Wed Aug 26 08:19:35 2015, mura...@pair.com wrote:
> > When two greps are used in parallel on one supply produced by
> > IO::Notification.watch_path, greps that match are triggered twice.
> > Run
> > the following code, then
On Tue, 20 Oct 2015 23:06:02 -0700, barto...@gmx.de wrote:
> Current failure mode:
>
> $ perl6-m -e 'say (1, 2).classify: -> $x { 1|2 }'
> P6opaque: no such attribute '$!reified'
> in block at -e:1
>
> $ perl6-m --version
> This is perl6 version 2015.09-431-g5d83db3 built on MoarVM version
>
On Thu, 12 Apr 2018 07:21:53 -0700, elizabeth wrote:
> Fixed with 344a64e987 , tests needed
>
> > On 24 Mar 2018, at 15:01, Aleks-Daniel Jakimenko-Aleksejev via RT
> > wrote:
> >
> > FWIW bisectable points to (2017-06-25)
> > htt
Further discussion on https://github.com/rakudo/rakudo/issues/1946
On 2017-05-28 21:20:08, c...@zoffix.com wrote:
> On Sun, 28 May 2017 18:18:14 -0700, raiph wrote:
> > If there hasn't been significant adoption of these tokens in extant
> > code then I'd personally +1 deprecation of them in v6.d
On Wed, 30 Jan 2013 07:17:38 -0800, masak wrote:
> rn: role F[$n] { method x { callsame; callsame until $.v % $n }
> }; class S { has $.v is rw = 1; method x { ++$.v } }; my $s = S.new; for
> ^3 { $s.x; say $s.v; $s = $s but F[$s.v] }
> niecza v24-18-gaf64300: OUTPUT«235»
> ..rakudo
On Wed, 30 Jan 2013 07:17:38 -0800, masak wrote:
> rn: role F[$n] { method x { callsame; callsame until $.v % $n }
> }; class S { has $.v is rw = 1; method x { ++$.v } }; my $s = S.new; for
> ^3 { $s.x; say $s.v; $s = $s but F[$s.v] }
> niecza v24-18-gaf64300: OUTPUT«235»
> ..rakudo
On Wed, 27 Jul 2016 12:29:11 -0700, coke wrote:
> Here's the test:
>
> my $c;
> ok 'abc' ~~ /.{ $c = $¢ }/, 'current match state';
> #?rakudo todo 'Type of $¢ is Any instead of Cursor - RT #124998'
> is $c.WHAT, Cursor.WHAT,'got right type';
>
> This might be a faulty test, however:
On Wed, 27 Jul 2016 12:29:11 -0700, coke wrote:
> Here's the test:
>
> my $c;
> ok 'abc' ~~ /.{ $c = $¢ }/, 'current match state';
> #?rakudo todo 'Type of $¢ is Any instead of Cursor - RT #124998'
> is $c.WHAT, Cursor.WHAT,'got right type';
>
> This might be a faulty test, however:
Re-opening this, as there's a much more common case where a typecheck of the
coercion result would be desired and that's when coercion results in a Failure:
m: multi sub foo(Int() $) { }; foo Inf
rakudo-moar 5a6ff4073: ( no output )
Re-opening this, as there's a much more common case where a typecheck of the
coercion result would be desired and that's when coercion results in a Failure:
m: multi sub foo(Int() $) { }; foo Inf
rakudo-moar 5a6ff4073: ( no output )
# New Ticket Created by Richard A Hogaboom
# Please include the string: [perl #133246]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133246 >
Attached is an executable file that demos a possible Perl 6 OO bug if
attributes
On Sat, 09 Jun 2018 05:33:04 -0700, c...@zoffix.com wrote:
> when
> using implicit return:
>
>
> method var1() is rw { return$!var }
> method var2() { return-rw $!var }
Correction, that should be:
method var1() is rw { $!var }
method var2() { return-rw $!var }
On Sat, 09 Jun 2018 05:33:04 -0700, c...@zoffix.com wrote:
> when
> using implicit return:
>
>
> method var1() is rw { return$!var }
> method var2() { return-rw $!var }
Correction, that should be:
method var1() is rw { $!var }
method var2() { return-rw $!var }
On Mon, 04 Jun 2018 07:31:40 -0700, richard.hogab...@gmail.com wrote:
> Attached is an executable file that demos a possible Perl 6 OO bug if
> attributes and method names are the same. This includes some compile
> time errors and an infinite loop.
>
Thanks for the report, but there's no bug
On Mon, 04 Jun 2018 07:31:40 -0700, richard.hogab...@gmail.com wrote:
> Attached is an executable file that demos a possible Perl 6 OO bug if
> attributes and method names are the same. This includes some compile
> time errors and an infinite loop.
>
Thanks for the report, but there's no bug
On Fri, 08 Jun 2018 15:24:32 -0700, alex.jakime...@gmail.com wrote:
> Golf:
>
> CONTROL {}; warn 42
>
> On 2018-06-08 15:11:08, comdog wrote:
> > While running this program I get a MoarVM panic:
> >
> > 2 + 2 = 4
> > 'two' is not numeric
> > MoarVM panic: Trying to unwind over wrong handler
> >
On Fri, 08 Jun 2018 15:24:32 -0700, alex.jakime...@gmail.com wrote:
> Golf:
>
> CONTROL {}; warn 42
>
> On 2018-06-08 15:11:08, comdog wrote:
> > While running this program I get a MoarVM panic:
> >
> > 2 + 2 = 4
> > 'two' is not numeric
> > MoarVM panic: Trying to unwind over wrong handler
> >
Golf:
CONTROL {}; warn 42
On 2018-06-08 15:11:08, comdog wrote:
> While running this program I get a MoarVM panic:
>
> 2 + 2 = 4
> 'two' is not numeric
> MoarVM panic: Trying to unwind over wrong handler
>
> The program:
>
> sub add-two-things ( $first, $second ) {
> CATCH {
> when
After https://github.com/rakudo/rakudo/commit/704b893c6a the last tests fudged
with this ticket are passing. I'm closing this ticket as 'resolved'.
On Mon, 21 May 2018 09:13:15 -0700, b...@abrij.org wrote:
> Note if we fix | to use fake infix adverbs, then we create the problem
> that |(1,1),(2,2),:f :g will be 1,1,:g,(2,2),:f.
...sorry that might be OK due to the "first pair in term position"...
but
|(1,1),(2,2),1 :g will be
Without the comma, the colonpair is in infix position, which means
it applies to the prefix unary | operator.
So whether this should be an error or "work" depends on what we can teach the |
operator to do with fake_infix adverbs it is passed.
Note if we fix | to use fake infix adverbs, then we
Data race is now fixed (in a post release branch):
Rakudo fix:
https://github.com/rakudo/rakudo/commit/6dd20588b6dfb75a121e2207df5f8c89aad3e1ef
Test: https://github.com/perl6/roast/commit/1d10e9dc12
1 - 100 of 16765 matches
Mail list logo
