> On 17 Aug 2017, at 18:11, Zoffix Znet via RT
> wrote:
>
> On Thu, 17 Aug 2017 08:50:48 -0700, alex.jakime...@gmail.com wrote:
>> See this...
>
> See also timotimo++'s comment that TimToady cleared a revert if there were
> fallout:
> raschipi, gfldex, timtoady already said he'd retract the
> On 17 Aug 2017, at 18:11, Zoffix Znet via RT
> wrote:
>
> On Thu, 17 Aug 2017 08:50:48 -0700, alex.jakime...@gmail.com wrote:
>> See this...
>
> See also timotimo++'s comment that TimToady cleared a revert if there were
> fallout:
> raschipi, gfldex, timtoady already said he'd retract the
> On 17 Aug 2017, at 17:50, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #131919]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Dis
> On 17 Aug 2017, at 17:50, Aleks-Daniel Jakimenko-Aleksejev (via RT)
> wrote:
>
> # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string: [perl #131919]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Dis
On Thu, 17 Aug 2017 09:11:21 -0700, c...@zoffix.com wrote:
> To me, it looks like a clear case for 6.d material. We made a promise
> to users that we won't make changes that break 6.c-errata changes and
> IMO the 6.c-errata roast changes due to this feature break that
> promise.
Though, since it'
On Thu, 17 Aug 2017 09:11:21 -0700, c...@zoffix.com wrote:
> To me, it looks like a clear case for 6.d material. We made a promise
> to users that we won't make changes that break 6.c-errata changes and
> IMO the 6.c-errata roast changes due to this feature break that
> promise.
Though, since it'
On Thu, 17 Aug 2017 08:50:48 -0700, alex.jakime...@gmail.com wrote:
> See this...
See also timotimo++'s comment that TimToady cleared a revert if there were
fallout:
raschipi, gfldex, timtoady already said he'd retract the commit if
there's ecosystem fallout, which you just demonstrated
https:
https://irclog.perlgeek.de/perl6-dev/2017-08-17#i_15032963
On 2017-08-16 14:30:42, alex.jakime...@gmail.com wrote:
> TL;DR it went from 59820 to 215976 after this commit:
>
https://github.com/rakudo/rakudo/commit/92bd7e4f54a92fa660f99b4d056d33a08fb98bd2
>
> Bisect log:
> https://gist.github.com/67
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #131919]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131919 >
See this commit:
https://github.com/rakudo/rakudo/commit/9501edae4f7
On Mon, 07 Aug 2017 19:48:36 -0700, ddgr...@gmail.com wrote:
> [22:44] m: sub foo(:color(:$colour)) { $colour + 1 }; my
> $s;
> for ^100 { $s += foo(:color($_)) }; say $s; say now - INIT now
> [22:44] <+camelia> rakudo-moar a91ad2: OUTPUT: «Unexpected named
> argument
> 'color' passed in sub
On Mon, 07 Aug 2017 19:48:36 -0700, ddgr...@gmail.com wrote:
> [22:44] m: sub foo(:color(:$colour)) { $colour + 1 }; my
> $s;
> for ^100 { $s += foo(:color($_)) }; say $s; say now - INIT now
> [22:44] <+camelia> rakudo-moar a91ad2: OUTPUT: «Unexpected named
> argument
> 'color' passed in sub
On Wed, 16 Aug 2017 14:53:05 -0700, alex.jakime...@gmail.com wrote:
> Also, it's not any different on HEAD:
>
> committable6test: 9658dd98c9dd8ec^^,9658dd98c9dd8ec,HEAD
> say
> "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
> AlexDaniel, ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9:
> «138
On Wed, 16 Aug 2017 14:53:05 -0700, alex.jakime...@gmail.com wrote:
> Also, it's not any different on HEAD:
>
> committable6test: 9658dd98c9dd8ec^^,9658dd98c9dd8ec,HEAD
> say
> "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024
> AlexDaniel, ¦9658dd98c9dd8ec^^: «58628» ¦9658dd9:
> «138
13 matches
Mail list logo
