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
Test was incorrect.
Fixed in https://github.com/perl6/roast/commit/771a2bbeb1
Test was incorrect.
Fixed in https://github.com/perl6/roast/commit/771a2bbeb1
Re-filed with more details on the issue in
https://github.com/rakudo/rakudo/issues/1830
> > >
> > > > On 29/12/2015 23:05, Timo Paulssen via RT wrote:
> > > > > On 12/29/2015 12:46 AM, Jules Field (via RT) wrote:
> > > > >> # New Ticket Created by Jules Field
> > > > >> # Please include the string:
https://github.com/rakudo/rakudo/issues/1361 has been fixed back in February
2018.
All three code snippets from this issue are failing with
X::Syntax::Variable::BadType now.
I've added a test to S12-coercion/coercion-types.t with commit
https://github.com/perl6/roast/commit/7fcc804bb9.
I'm
This was fixed on MoarVM for https://github.com/rakudo/rakudo/issues/1216
Tests added for the variants in this ticket in
https://github.com/perl6/roast/commit/fe57091172
JVM apparently still needs work on this, so the tests are skipped for JVM.
keeping open for JVM fixes.
Current behavior seems to be satisfactory now:
$ perl6 -e 'role R { has $.x }; role S does R { has $.x }; S.new;'
Attribute '$!x' conflicts in role composition
Test added in https://github.com/perl6/roast/commit/c65ed93912
closing.
The examples would fail usage constraints with the parameterless MAIN.
I could not get them to fail with any internal messages on current rakudo,
either with the parameterless MAIN or with a MAIN that had a :$y.
Haven't looked as to when this got fixed.
Tests added for both cases (though I had
I'm closing this ticket, cmp. https://github.com/rakudo/rakudo/issues/1797:
> #124552 can be closed. Test was working but skipped. Unskipped in roast now.
Test PR for rakudo tree: https://github.com/rakudo/rakudo/pull/1806
If that is accepted, someone with a jvm build should check whether it needs to
be fudged for rakudo-j
and if it is fine there as well, this ticket can be closed.
Golf and change of behavior:
$ perl6 -e 'use NativeCall; class T is repr is export { sub
new(size_t $n) returns T is symbol is native { * }; }; T.new();'
$ perl6 -e 'use NativeCall; class T {...}; class T is repr is export
{ sub new(size_t $n) returns T is symbol is native { * }; }; T.new();'
This is a very old ticket and we no longer have postcircumfix:<( )>
for objects.
If you redo the example to use CALL-ME it still does not call the
original class method, however, CALL-ME is defined as a submethod,
not a method, and testing the difference:
$ perl6 -e 'class S { method x {
Well, the current test file succeeds in both cases. This ticket is so old
it may more be the tests have changed than anything else, but there was
also lot of charset work so maybe it is actually fixed.
If you can still figure out how to break something with LC_ALL,
please re-file a github issue
spam rejected
spam rejected
This is also an issue in nqp.
$ nqp -e 'grammar f { regex TOP { ^ $ }; regex foo($i) { .. } };
nqp::say(f.parse("aaa"));'
Too few positionals passed; expected 2 arguments but got 1
Fixing it in nqp first is probably the best first step. To
that end I investigated some and it looks
This has been fixed with https://github.com/perl6/nqp/commit/075ff765f5
The test in S05-mass/rx.t passes, so I'm closing this ticket was 'resolved'.
This has been fixed with https://github.com/perl6/nqp/commit/075ff765f5
The tests in S05-metasyntax/lookaround.t are passing, so I'm closing this
ticket was 'resolved'.
I'm closing this ticket, cmp. https://github.com/rakudo/rakudo/issues/1797:
> #124738 can be closed because the roast test was wrong, trying to use a m//
> where an rx// was intended.
> Fixed by samcv in roast commit
> https://github.com/perl6/roast/commit/659fcf44b0
# New Ticket Created by Ben Sauvin
# Please include the string: [perl #133162]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133162 >
I'm trying to run this code:
my $n;
await IO::Socket::Async.connect('127.0.0.1',
The issue with .unique was resolved in these commits
Rakudo:
https://github.com/rakudo/rakudo/commit/8cd70d1ee3e17fad78ae5daf0890d1cfb74c2deb
Roast:
https://github.com/perl6/roast/commit/ad38801161c518a3cf3bca9012db973851c4b0c3
Roast:
On Tue, 02 Aug 2016 09:51:31 -0700, zef...@fysh.org wrote:
> > (1180591620717411303424.0e0).Int
> 1180591620717411303424
> > (1180591620717411303424.0e0).perl.EVAL.Int
> 1180591620717409992704
>
> The .perl.EVAL process ought to yield the same value we started with.
> It's coming back as a
On Tue, 02 Aug 2016 09:51:31 -0700, zef...@fysh.org wrote:
> > (1180591620717411303424.0e0).Int
> 1180591620717411303424
> > (1180591620717411303424.0e0).perl.EVAL.Int
> 1180591620717409992704
>
> The .perl.EVAL process ought to yield the same value we started with.
> It's coming back as a
On Tue, 02 Aug 2016 10:44:50 -0700, zef...@fysh.org wrote:
> > my $a = 1180591620717411303424e0
> 1.18059162071741e+21
> > my $b = 1180591620717409992704e0
> 1.18059162071741e+21
> > $a.Int
> 1180591620717411303424
> > $b.Int
> 1180591620717409992704
> > $a == $b
> False
> > $a === $b
> False
> >
On Tue, 02 Aug 2016 10:44:50 -0700, zef...@fysh.org wrote:
> > my $a = 1180591620717411303424e0
> 1.18059162071741e+21
> > my $b = 1180591620717409992704e0
> 1.18059162071741e+21
> > $a.Int
> 1180591620717411303424
> > $b.Int
> 1180591620717409992704
> > $a == $b
> False
> > $a === $b
> False
> >
On Tue, 02 Aug 2016 10:55:34 -0700, zef...@fysh.org wrote:
> > 1180591620717411303424e0 == 1180591620717409992704e0
> True
> > 1180591620717411303424e0 === 1180591620717409992704e0
> True
>
> Say what? These are distinct Num values, differing by 10 ulp.
> These literals work fine in other
On Tue, 02 Aug 2016 10:55:34 -0700, zef...@fysh.org wrote:
> > 1180591620717411303424e0 == 1180591620717409992704e0
> True
> > 1180591620717411303424e0 === 1180591620717409992704e0
> True
>
> Say what? These are distinct Num values, differing by 10 ulp.
> These literals work fine in other
On Fri, 12 Aug 2016 10:24:48 -0700, zef...@fysh.org wrote:
> > "9.998e0".EVAL - "9.998e0".Num
> 1.77635683940025e-15
>
> Observe that the same string yields different Num values when interpreted
> as a Num literal and when coerced. Where the string is meaningful both
>
On Fri, 12 Aug 2016 10:24:48 -0700, zef...@fysh.org wrote:
> > "9.998e0".EVAL - "9.998e0".Num
> 1.77635683940025e-15
>
> Observe that the same string yields different Num values when interpreted
> as a Num literal and when coerced. Where the string is meaningful both
>
On Thu, 12 Apr 2018 23:34:43 -0700, mar...@senfdax.de wrote:
> requireing a non installed module leads to strange error if the name
> starts with the name of a core module. e.g:
>
>
> > perl6 -e 'require IO::Socket::Async::SSL'
> IO::Socket::Async::SSL is a builtin type, not an external module
On Thu, 12 Apr 2018 23:34:43 -0700, mar...@senfdax.de wrote:
> requireing a non installed module leads to strange error if the name
> starts with the name of a core module. e.g:
>
>
> > perl6 -e 'require IO::Socket::Async::SSL'
> IO::Socket::Async::SSL is a builtin type, not an external module
On Fri, 20 Oct 2017 07:34:04 -0700, victor.a...@derpymail.org wrote:
> How to reproduce
>
>
> perl6 -e 'my ($a, $b) = (0.7,
> 0.71); say $a <=> $b, " ", Num($a) <=> Num($b)'
>
> Expected behavior
> -
>
> Prints `Less
On Fri, 20 Oct 2017 07:34:04 -0700, victor.a...@derpymail.org wrote:
> How to reproduce
>
>
> perl6 -e 'my ($a, $b) = (0.7,
> 0.71); say $a <=> $b, " ", Num($a) <=> Num($b)'
>
> Expected behavior
> -
>
> Prints `Less
doesn’t exist. I guess
we can build some heuristic check on that, but it feels fragile. Perhaps nine
/ ugexe / jnthn have a better idea about that.
> On 13 Apr 2018, at 08:34, Martin Barth (via RT)
> <perl6-bugs-follo...@perl.org> wrote:
>
> # New Ticket Created by Martin
On Fri, 12 Aug 2016 10:00:17 -0700, zef...@fysh.org wrote:
> > "9.9981e0".EVAL < "9.998e0".EVAL
> True
>
> Observe that the literal with a greater nominal value yields a lower
> Num value. (The .EVAL circumlocution is required to work around [perl
> #128820].) This
On Fri, 12 Aug 2016 10:00:17 -0700, zef...@fysh.org wrote:
> > "9.9981e0".EVAL < "9.998e0".EVAL
> True
>
> Observe that the literal with a greater nominal value yields a lower
> Num value. (The .EVAL circumlocution is required to work around [perl
> #128820].) This
# New Ticket Created by Martin Barth
# Please include the string: [perl #133107]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133107 >
requireing a non installed module leads to strange error if the name
starts with the
Fixed with 344a64e987 , tests needed
> On 24 Mar 2018, at 15:01, Aleks-Daniel Jakimenko-Aleksejev via RT
> <perl6-bugs-follo...@perl.org> wrote:
>
> FWIW bisectable points to (2017-06-25)
> https://github.com/rakudo/rakudo/commit/a2133dbc6a00d1f87bb0644c829591144
https://github.com/rakudo/rakudo/pull/1722#issuecomment-380779444
On 2017-10-12 22:37:24, alex.jakime...@gmail.com wrote:
> Code:
> say "blogger".comb.Bag # if you want for all the letters
>
> ¦«2015.12»:
> bag(r, l, g(2), b, e, o)
>
> ¦«2016.06»:
> bag(r, l, g(2), b, e, o)
>
> ¦«2016.12»:
>
Tests were added in this PR: https://github.com/rakudo/rakudo/pull/1715
Closing
On 2017-12-02 04:17:46, alex.jakime...@gmail.com wrote:
> Not quite sure what to do with this ticket.
>
> The output varies across releases:
> https://gist.github.com/Whateverable/54e87afdbb2d88d2a959527b255681af
>
>
Test added in
https://github.com/perl6/roast/commit/1f171a9d2f0dd973a5e0d5c0c34a6f50b91da81f
Closing
On 2018-03-08 10:28:12, jan-olof.hen...@bredband.net wrote:
> On Fri, 27 Nov 2015 12:30:15 -0800, zengargo...@gmail.com wrote:
> > autarch noticed an oddness in File::Temp when used with .hyper:
On 19 Oct 2015, at 03:42, Carsten Hartenfels (via RT) > > follo...@perl.org> wrote:
> > >
> > > # New Ticket Created by Carsten Hartenfels
> > > # Please include the string: [perl #126394]
> > > # in the subject line of all future correspondence about
jmerelo++ brought this ticket to my attention during the squashathon and
suggested that this ticket can be closed.
I've tried reproducing the issue with the provided tarball and couldn't. In
fact, the Makefile in that tarball no longer works as expected because things
are very different now.
reverted c63c57e9a823303e74c06 for now
> >
> > > On 8 Aug 2017, at 12:21, Zoffix Znet (via RT) > > follo...@perl.org> wrote:
> > >
> > > # New Ticket Created by Zoffix Znet
> > > # Please include the string: [perl #131858]
> > > # in
A test for this issue was already added in
https://github.com/rakudo/rakudo/commit/f3efe5e6b4a9ee5#diff-2aaee6bee3c5525182362ffdcbea1f2cR14
Closing.
On 2018-03-10 16:40:40, jan-olof.hen...@bredband.net wrote:
> On Thu, 22 Jun 2017 05:25:08 -0700, c...@zoffix.com wrote:
> > A WhateverCode
Tests in
https://github.com/perl6/roast/commit/b320464868d3b8da98c090ddc4b0d57604683e13
Closing
On 2018-03-10 11:25:06, jan-olof.hen...@bredband.net wrote:
> On Wed, 22 Feb 2017 03:59:05 -0800, elizabeth wrote:
> > > On 22 Feb 2017, at 12:41, jn...@jnthn.net via RT > > follo.
Tests added in
https://github.com/perl6/roast/commit/d78f33966cf6a6ec6bc060d98dfc521ad59b6f75
Closing
On 2018-02-06 14:12:56, jan-olof.hen...@bredband.net wrote:
> On Sat, 07 May 2016 13:26:09 -0700, sml...@gmail.com wrote:
> > Confirmed on current Rakudo.
> >
> > Interestingly, it works if `for
> > > I'll be
> > > > linking issues here so that we have all things in one place.
> > > >
> > > > IO::MiddleMan and Lumberjack:
> > > > https://github.com/zoffixznet/perl6-IO-MiddleMan/issues/5
> > > > On 2017-09-11 04:18:39, eliza
Tests in
https://github.com/perl6/roast/commit/1a42efd4ce0fdc695b16bbf64af92ecf0bca1866
On 2018-03-10 10:43:14, alex.jakime...@gmail.com wrote:
> This ticket now needs tests, further discussion related issues here:
> https://github.com/rakudo/rakudo/issues/1607
>
> On 2017-03-08 05:56:13,
On Fri, 16 Mar 2018 16:02:15 -0700, jan-olof.hen...@bredband.net wrote:
> On Tue, 30 Aug 2016 16:30:24 -0700, allber...@gmail.com wrote:
> > I think the problem is that there's already another syntax using that
> > sequence: coercion types. FF(FF(2)) is being parsed as a coercion
> > type from
> >
Segfault mentioned above is already tested and the test was unfudged in
https://github.com/perl6/roast/commit/ef7b0da83d#diff-72b101ff62a0582672d4de2788ffa1bbL77
Closing
On 2018-03-12 08:29:49, jan-olof.hen...@bredband.net wrote:
> On Mon, 16 Oct 2017 13:04:48 -0700, barto...@gmx.de wrote:
> > On
Tests in
https://github.com/perl6/roast/commit/79dff96fc9f383616dd192ef016725395323887b
and
https://github.com/perl6/roast/commit/82d3a883a52af23c8a67e46b88b313b3cf20b18d
On 2018-03-10 06:26:00, jan-olof.hen...@bredband.net wrote:
> On Wed, 04 Jan 2017 15:02:45 -0800, alex.jakime...@gmail.com
Tests in
https://github.com/perl6/roast/commit/ce1a5a2e6b5b199c0df69a83cf66f1b830ee47e8
and
https://github.com/perl6/roast/commit/38c9dc5fd5339ed434438eb58bae07e7fdd31a1d
Closing.
On 2018-03-12 06:59:31, jan-olof.hen...@bredband.net wrote:
> On Wed, 13 Sep 2017 19:17:16 -0700, b...@abrij.org
# New Ticket Created by Martin Barth
# Please include the string: [perl #133082]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133082 >
Hello,
IMHO the error could be better:
perl6 -e 'my %foo = ; say !%foo:exists'
On Sat, 15 Jul 2017 09:49:10 -0700, jan-olof.hen...@bredband.net wrote:
> On Fri, 15 Jul 2016 02:45:51 -0700, mt1...@gmail.com wrote:
> > Hi,
> >
> > Old code gives now error in Rakudo version 2016.06-234-g0189851 built
> > on
> > MoarVM version 2016.06-9-g8fc21d5.
> >
> > Code is
> >
> > sub
On Sat, 15 Jul 2017 09:49:10 -0700, jan-olof.hen...@bredband.net wrote:
> On Fri, 15 Jul 2016 02:45:51 -0700, mt1...@gmail.com wrote:
> > Hi,
> >
> > Old code gives now error in Rakudo version 2016.06-234-g0189851 built
> > on
> > MoarVM version 2016.06-9-g8fc21d5.
> >
> > Code is
> >
> > sub
There are also issues with libssl (which I think the IO::Socket::SSL module
calls using Native Call) and threads.
At the moment the only threads safe https client is the Cro one, I believe.
Sorry I can't be more help, 2am insomnia should really be sleeping.
On Wed, 4 Apr 2018, 2:30 am Simon
Looks to me like one of the sites is redirecting to an https page and you
don't have IO::Socket::SSL installed.
On Wed, 4 Apr 2018, 1:42 am brian d foy,
wrote:
> # New Ticket Created by "brian d foy"
> # Please include the string: [perl #133057]
> # in the
The error message isn't useful because you get that no matter what
happens. It's really the IO::Socket::SSL is not thread safe.
But, I'd not expect a segfault.
Ah, there's even an HTTP::UserAgent issue for this I think:
https://github.com/sergot/http-useragent/issues/191
On Mon, 20 Feb 2017 06:39:32 -0800, ronaldxs wrote:
> jnthn mentioned on irc awareness of at least one more leak
> (presumably) related to this ticket and so ticket waits on news of
> fixing further leak(s).
Running the example above one a 32-bit Linux VM I get:
This Rakudo version is
On Sun, 25 Mar 2018 08:43:30 -0700, jan-olof.hen...@bredband.net wrote:
> On Thu, 29 Jun 2017 12:50:43 -0700, sml...@gmail.com wrote:
> > It looks like this bug hasn't been *completely* fixed:
> >
> > dd :<+>( "2" ); # 2
> > dd :<*>( "2" ); # 2
> >
> > dd [*] "2"; # 2
>
On Fri, 12 Aug 2016 10:24:48 -0700, zef...@fysh.org wrote:
> > "9.998e0".EVAL - "9.998e0".Num
> 1.77635683940025e-15
>
> Observe that the same string yields different Num values when interpreted
> as a Num literal and when coerced. Where the string is meaningful both
>
On Fri, 12 Aug 2016 10:24:48 -0700, zef...@fysh.org wrote:
> > "9.998e0".EVAL - "9.998e0".Num
> 1.77635683940025e-15
>
> Observe that the same string yields different Num values when interpreted
> as a Num literal and when coerced. Where the string is meaningful both
>
On Fri, 12 Aug 2016 09:46:38 -0700, zef...@fysh.org wrote:
> > (9.999e-5 * 2e0**66).Int * 5**8 - * 2**58
> 287369
> > (9.99895e-5 * 2e0**66).Int * 5**8 - * 2**58
> -103256
>
> The above computations show, scaled up, the difference between a Num value
> and the exact value
On Fri, 12 Aug 2016 09:46:38 -0700, zef...@fysh.org wrote:
> > (9.999e-5 * 2e0**66).Int * 5**8 - * 2**58
> 287369
> > (9.99895e-5 * 2e0**66).Int * 5**8 - * 2**58
> -103256
>
> The above computations show, scaled up, the difference between a Num value
> and the exact value
On Wed, 11 Oct 2017 04:25:32 -0700, sisyphus wrote:
> Hi,
> Some anomalous rounding behaviour on Ubuntu-16.04 was noted at
> http://www.perlmonks.org/?node_id=1200326
>
> Here are the specifics:
>
> $ perl6 --version
> This is Rakudo version 2017.07 built on MoarVM version 2017.07
>
On Wed, 11 Oct 2017 04:25:32 -0700, sisyphus wrote:
> Hi,
> Some anomalous rounding behaviour on Ubuntu-16.04 was noted at
> http://www.perlmonks.org/?node_id=1200326
>
> Here are the specifics:
>
> $ perl6 --version
> This is Rakudo version 2017.07 built on MoarVM version 2017.07
>
On Wed, 06 Jan 2016 04:47:03 -0800, dankogai wrote:
> Folks,
>
> Rakudo needs to add one more digit for each Num it stringifies.
>
> % perl6 -e 'pi.say'
> 3.14159265358979
> % ruby -e 'puts Math::PI'
> 3.141592653589793
>
> As a result…
>
> % perl6
> > 3.14159265358979 == pi
> False
> >
On Wed, 06 Jan 2016 04:47:03 -0800, dankogai wrote:
> Folks,
>
> Rakudo needs to add one more digit for each Num it stringifies.
>
> % perl6 -e 'pi.say'
> 3.14159265358979
> % ruby -e 'puts Math::PI'
> 3.141592653589793
>
> As a result…
>
> % perl6
> > 3.14159265358979 == pi
> False
> >
On Thu, 29 Jun 2017 12:50:43 -0700, sml...@gmail.com wrote:
> It looks like this bug hasn't been *completely* fixed:
>
> dd :<+>( "2" ); # 2
> dd :<*>( "2" ); # 2
>
> dd [*] "2"; # 2
> dd [+] "2"; # 2
>
> dd reduce :<*>, "2"; # 2
> dd reduce :<+>,
Some extra info:
Output on all releases (not a regression because the output was always wrong):
https://gist.github.com/b4b27b8088a230a6051d634dc7b2d13e
The change in behavior happened in (2017-03-21)
https://github.com/rakudo/rakudo/commit/16f950b30572e0fa584ddfab1e84e5ef0ca5dfc9
Which links
18, at 15:04, Nick Wellnhofer (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by Nick Wellnhofer
> > # Please include the string: [perl #133016]
> > # in the subject line of all future correspondence about this issue.
> > # https://rt.perl.org/T
That does indeed look wrong to me, investigating
> On 23 Mar 2018, at 15:04, Nick Wellnhofer (via RT)
> <perl6-bugs-follo...@perl.org> wrote:
>
> # New Ticket Created by Nick Wellnhofer
> # Please include the string: [perl #133016]
> # in the subject line of all fut
# New Ticket Created by Nick Wellnhofer
# Please include the string: [perl #133017]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133017 >
When using a reduction operator with the "intermediate results" option
combined with
# New Ticket Created by Nick Wellnhofer
# Please include the string: [perl #133016]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133016 >
I get an unexpected result when subtracting a List from a Bag with the set
On Tue, 13 Mar 2018 14:50:17 -0700, jan-olof.hen...@bredband.net wrote:
> On Fri, 05 Aug 2016 18:04:36 -0700, c...@zoffix.com wrote:
> > Still present today:
> >
> > m: my $sepreg = rx/(<[\\/]>)/; my $filenameW =
> > "c:\\g\\b.mp4"; $filenameW ~~ $sepreg; say $/;
> > rakudo-moar 589061:
Fixed with https://github.com/rakudo/rakudo/commit/bdd8143e6f, tests needed
> On 1 Jul 2017, at 15:20, Jan-Olof Hendig (via RT)
> <perl6-bugs-follo...@perl.org> wrote:
>
> # New Ticket Created by Jan-Olof Hendig
> # Please include the string: [perl #131684]
> # in
Closing this in favor of https://github.com/rakudo/rakudo/issues/1638
On 2015-10-17 06:27:53, r...@hoelz.ro wrote:
> As far as I can tell, MoarVM doesn't pass any information about a
> child process' PID to the caller of async proc operations; if it does,
> that information isn't exposed at the
Closing this in favor of https://github.com/rakudo/rakudo/issues/1638
On 2017-10-02 00:09:23, alex.jakime...@gmail.com wrote:
> Oh, actually, I noticed it too a few months ago. And removed it.
>
https://github.com/rakudo/rakudo/commit/5b8d4c2f4232dc0e5e9c62dc602fdcb74f7bdd24#diff-
>
On Thu, 13 Apr 2017 12:21:57 -0700, barto...@gmx.de wrote:
> [...] then we should
>
> * change the implementation for the JVM backend so that the newly
> added tests pass
The tests for open modes are passing now on the JVM backend. I'm closing this
ticket as 'resolved'.
Further discussion on https://github.com/rakudo/rakudo/issues/1622.
On 2017-01-21 14:13:42, jn...@jnthn.net wrote:
> On Wed, 18 Jan 2017 18:16:20 -0800, c...@zoffix.com wrote:
> > the :sigspace adverb does not affect spaces inside character class.
> > Should it?
> >
> No, I don't think so.
On Wed, 14 Mar 2018 13:28:05 -0700, jan-olof.hen...@bredband.net wrote:
> On Sun, 26 Feb 2017 23:01:18 -0800, zef...@fysh.org wrote:
> > This problem no longer occurs.
> >
> > -zefram
> >
>
> Fixed with commit (2017-01-02)
>
On Wed, 14 Mar 2018 13:26:11 -0700, jan-olof.hen...@bredband.net wrote:
> On Sun, 26 Feb 2017 23:02:00 -0800, zef...@fysh.org wrote:
> > This problem no longer occurs.
> >
> > -zefram
> >
>
> This was fixed with commit (2017-01-02)
>
On Sat, 11 Mar 2017 03:02:39 -0800, elizabeth wrote:
> $ 6 'my $a = 0; ($a++,) Zxx 42; say $a’
> 0
>
> $ 6 'my $a = 0; ($a++,) Xxx 42; say $a’
> 0
>
> Before https://github.com/rakudo/rakudo/commit/1754dc5f7e , this would
> have yielded 42 in both cases. However, this was a side-effect (pun
>
On Wed, 04 Jan 2017 21:27:05 -0800, samant...@posteo.net wrote:
> Also see this bisectable results:
> https://gist.github.com/Whateverable/50acf5fe072680085746459f144a106f
>
> You can see how with the new commit, 'space' and 'White_Space' now
> resolve to the same property. Before 'space'
On Tue, 30 Aug 2016 16:30:24 -0700, allber...@gmail.com wrote:
> I think the problem is that there's already another syntax using that
> sequence: coercion types. FF(FF(2)) is being parsed as a coercion type from
> FF to FF(... and then it falls over because it's not expecting nested
> coercion
On Mon, 03 Jul 2017 14:16:58 -0700, allber...@gmail.com wrote:
> [03 21:03:27] m: use NativeCall; sub foo(num $a) is
> native("foo") { * };
> [03 21:03:27] rakudo-moar a7b230: OUTPUT: «===SORRY!=== Error
> while compiling 
> [03 21:03:27] Cannot resolve caller infix:<==>(NQPMu, Int); none of
# New Ticket Created by Ron Schmidt
# Please include the string: [perl #132983]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132983 >
Roast S32-io/IO-Socket-Async.t has a test for a second tap on a Supply
from listen which
On Wed, 14 Mar 2018 14:16:06 -0700, comdog wrote:
> I was playing with coercion types and wondered what would happen if
> a .Int method did not return the right sort of type:
>
> class Foo {
> method Int ( --> Str ) { 'Hello' }
> }
>
> put try-it( Foo.new );
>
> sub
On Wed, 14 Mar 2018 14:16:06 -0700, comdog wrote:
> I was playing with coercion types and wondered what would happen if
> a .Int method did not return the right sort of type:
>
> class Foo {
> method Int ( --> Str ) { 'Hello' }
> }
>
> put try-it( Foo.new );
>
> sub
On Mon, 17 Jul 2017 10:50:55 -0700, ug...@cpan.org wrote:
> The %?RESOURCES bug was fixed in: https://github.com/rakudo/rakudo/pull/1106
ugexe, does that mean that the issue can be marked as resolved?
On Mon, 24 Jul 2017 09:09:55 -0700, c...@zoffix.com wrote:
> m: my @a is default(42) = 1...*; @a[1]:delete; say @a[1]:exists; .say
> for @a[^10]
> rakudo-moar 2fb8c7: OUTPUT: «True12345678910»
>
> Expected: reify until `1`, delete it, and have `@a[1]:exists` give
> False, and `.say for
On Sun, 26 Feb 2017 23:01:18 -0800, zef...@fysh.org wrote:
> This problem no longer occurs.
>
> -zefram
>
Fixed with commit (2017-01-02)
https://github.com/rakudo/rakudo/commit/7c8b705b3375522fc36304b771f82f50246afcf0
On Sun, 26 Feb 2017 23:02:00 -0800, zef...@fysh.org wrote:
> This problem no longer occurs.
>
> -zefram
>
This was fixed with commit (2017-01-02)
https://github.com/rakudo/rakudo/commit/7c8b705b3375522fc36304b771f82f50246afcf0
When I run this example now (Windows and Linux) I get:
P6opaque: no such attribute '$!encoded-string' on type Codeword in a Proxy when
trying to get a value
instead of a segfault. If I tweak the code as below to use subs instead of
methods for the Proxy hooks it runs fine. The P6opaque error
On Fri, 05 Aug 2016 18:04:36 -0700, c...@zoffix.com wrote:
> Still present today:
>
> m: my $sepreg = rx/(<[\\/]>)/; my $filenameW =
> "c:\\g\\b.mp4"; $filenameW ~~ $sepreg; say $/;
> rakudo-moar 589061: OUTPUT«「\」 0 => 「\」»
> m: constant $sepreg = rx/(<[\\/]>)/; my $filenameW =
>
Pretty sure this is a dup of https://github.com/rakudo/rakudo/issues/1515 , you
can follow the progress on the issue there. Let us know if your problem is
actually different.
Closing
On 2018-02-25 11:11:55, mt1...@gmail.com wrote:
> Hi,
>
> According to the documentation one should use the
On Mon, 21 Dec 2015 11:09:40 -0800, zef...@fysh.org wrote:
> Elizabeth Mattijsen via RT wrote:
> >All of that goodness now in 591783d116a56d4b2c54f .
>
> You left a stray line in IO::Path.perl, which calls PERLIFY-STR in
> sink context.
>
> >Indeed! Now, if this ha
101 - 200 of 16765 matches
Mail list logo