[perl #130488] [LTA] Trying to output something unrepresentable in the encoding throws X::AdHoc

On Mon, 02 Jan 2017 16:35:46 -0800, comdog wrote: > Trying to output a character unrepresentable in the specified > encoding throws an X::AdHoc error. I think that should be X::IO, > and maybe there's enough issues here that an X::IO::Exception may > be interesting enough. > > my $file = 'enco

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/13/2017 01:36 PM, Trey Harris wrote: On Sat, Sep 9, 2017 at 3:55 PM ToddAndMargo toddandma...@zoho.com wrote: On 09/09/2017 07:00 AM, Timo Paulssen wrote: > This should be enlig

[perl #131162] [BUG][GLR] .splice loses containerization on replacement value

On Sun, 16 Apr 2017 12:56:58 -0700, elizabeth wrote: > Actually reported as a SO question by brian d foy: > > http://stackoverflow.com/questions/43437664/how-can-i-get-around-a- > slurpy-parameter-in-the-perl-6-signature > > > m: my @a = [1,1],[2,2],[3,3]; dd @a; @a.splice: 0, 2, > $[4,4

What is this things official name?

Hi All, When you see things like > method getc(IO::Handle:D: --> Str:D) > multi sub getc (IO::Handle $fh = $*ARGFILES --> Str:D) in the documentation pages, what is the official name? Many thanks, -T

Re: Who called me?

On 09/13/2017 04:56 PM, ToddAndMargo wrote: Hi All, I am trying to convert this from Perl 5: my $WhoCalledMe = ( caller(0) )[1]; I use it inside a sub to determine who called the sub. How is this done in P6? Many thanks, -T Follow up: With a lot of help from the chat line, it transp

Re: :: question

On 09/13/2017 10:57 PM, Brandon Allbery wrote: On Thu, Sep 14, 2017 at 1:48 AM, Brandon Allbery > wrote: If you want to use the other way, the CheckSystemDependency module MUST define Which as: our sub Which ... If it is not explicitly declared "our", then

[perl #132097] [REGRESSION] Some issue with BUILDPLAN changes

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132097] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132097 > Submitting this ticket just to add some context for the upcoming test

Re: Any "note" without the "say"?

On 09/15/2017 02:05 PM, ToddAndMargo wrote: On 09/15/2017 01:54 PM, Brandon Allbery wrote: On Fri, Sep 15, 2017 at 4:51 PM, ToddAndMargo > wrote: On 09/15/2017 01:29 PM, Brandon Allbery wrote: Everyone does at one time :) It's really useful for debuggi

Re: Any "note" without the "say"?

On 09/15/2017 01:54 PM, Brandon Allbery wrote: On Fri, Sep 15, 2017 at 4:51 PM, ToddAndMargo > wrote: On 09/15/2017 01:29 PM, Brandon Allbery wrote: Everyone does at one time :) It's really useful for debugging, but you generally strip it out of

Re: Any "note" without the "say"?

On 09/15/2017 01:48 PM, Andy Bach wrote: So "note" $ perl6 -e 'note "hi mom"' > /dev/null hi mom replaces "warn ...\n" or $ perl6 -e 'warn "hi mom\n"' > /dev/null hi mom in block at -e line 1 have I forgotten my p6 newline syntax (again)? Hi Andy, Oh goody. I get to help someone for

Re: Any "note" without the "say"?

On Fri, Sep 15, 2017 at 04:54:33PM -0400, Brandon Allbery wrote: > On Fri, Sep 15, 2017 at 4:51 PM, ToddAndMargo wrote: > > On 09/15/2017 01:29 PM, Brandon Allbery wrote: > >> Everyone does at one time :) It's really useful for debugging, but you > >> generally strip it out of production code. > >

Re: Any "note" without the "say"?

On Fri, Sep 15, 2017 at 4:51 PM, ToddAndMargo wrote: > On 09/15/2017 01:29 PM, Brandon Allbery wrote: > >> Everyone does at one time :) It's really useful for debugging, but you >> generally strip it out of production code. >> > > I saw a business study somewhere (I don't remember where) > that d

Re: Any "note" without the "say"?

On 09/15/2017 01:29 PM, Brandon Allbery wrote: Thank you for the confirmation. Searching for something like this brings up a bazillion Perl 5 hits. Oh well, neither is "note". Someone must have had a special need for it at one time. Everyone does at one time :) It's really

Re: Any "note" without the "say"?

> > > Oh well, neither is "note". Someone must have > had a special need for it at one time. > > Everyone does at one time :) It's really useful for debugging, but you generally strip it out of production code. So "note" $ perl6 -e 'note "hi mom"' > /dev/null hi mom replaces "warn ...\n" or $

Re: Any "note" without the "say"?

On Fri, Sep 15, 2017 at 4:02 PM, ToddAndMargo wrote: > On 09/15/2017 12:52 PM, Brandon Allbery wrote: > >> On Fri, Sep 15, 2017 at 3:48 PM, ToddAndMargo > > wrote: >> >> Is there a similar "print" to the STDERR for when >> you don't want the cr-lf inserted? >

[perl #132093] Enum.succ and Enum.pred are O(n)

Well, as long as it benefits the "very fucking close", amirite? Take care of the conch.

Re: Any "note" without the "say"?

On 09/15/2017 12:52 PM, Brandon Allbery wrote: On Fri, Sep 15, 2017 at 3:48 PM, ToddAndMargo > wrote: Is there a similar "print" to the STDERR for when you don't want the cr-lf inserted? The hard way: $*ERR.print: "print to std err\n"; That's it.

[perl #132032] [BUG] List.new loses Nil

On Fri, 15 Sep 2017 11:47:10 -0700, c...@zoffix.com wrote: > On Tue, 05 Sep 2017 03:19:45 -0700, zef...@fysh.org wrote: > > > (3, Nil) > > (3 Nil) > > > List.new(3, Nil) > > (3 (Any)) > > > > It is possible (as it should be) to put Nil into a List, if it's > > constructed using the comma operator.

Re: Any "note" without the "say"?

On Fri, Sep 15, 2017 at 3:48 PM, ToddAndMargo wrote: > Is there a similar "print" to the STDERR for when > you don't want the cr-lf inserted? > > The hard way: > $*ERR.print: "print to std err\n"; > That's it. It's not really common enough to deserve something shorter. -- brandon s allbery kf8

Any "note" without the "say"?

Hi All, Thanks to the guys on the chat line, I found out about "note", which is "say" to the STDERR. Is there a similar "print" to the STDERR for when you don't want the cr-lf inserted? The hard way: $*ERR.print: "print to std err\n"; Many thanks, -T

[perl #132032] [BUG] List.new loses Nil

On Tue, 05 Sep 2017 03:19:45 -0700, zef...@fysh.org wrote: > > (3, Nil) > (3 Nil) > > List.new(3, Nil) > (3 (Any)) > > It is possible (as it should be) to put Nil into a List, if it's > constructed using the comma operator. But constructing it via the > List.new() constructor replaces the Nil wit

[perl #132032] [BUG] List.new loses Nil

On Tue, 05 Sep 2017 03:19:45 -0700, zef...@fysh.org wrote: > > (3, Nil) > (3 Nil) > > List.new(3, Nil) > (3 (Any)) > > It is possible (as it should be) to put Nil into a List, if it's > constructed using the comma operator. But constructing it via the > List.new() constructor replaces the Nil wit

[perl #132093] Enum.succ and Enum.pred are O(n)

Now resolved in https://github.com/rakudo/rakudo/commit/f925c64826f78803969bb43398877309f6b4a1ac Closing. On 2017-09-15 09:01:04, alex.jakime...@gmail.com wrote: > Well, the title says “Enum.succ and Enum.pred are O(n)” and the issue > is still > there, so this ticket is definitely not resolved.

[perl #132093] Enum.succ and Enum.pred are O(n)

Well, the title says “Enum.succ and Enum.pred are O(n)” and the issue is still there, so this ticket is definitely not resolved. If anything, it was rejected. However, the reasoning for keeping O(n) kinda contradicts itself. If we're trading RAM for performance, and the amount of elements in enums

[perl #128717] [LTA] react whenever throws a cryptic error

On Sat, 23 Jul 2016 20:36:59 -0700, c...@zoffix.com wrote: > Blockless `react` seems to be unsupported and the error message it > throws is cryptic and unrelated to the actual issue. Best would be if > it actually worked, but at least the error message should be improved. > > $ perl6 -e 'react whe

[perl #128717] [LTA] react whenever throws a cryptic error

On Sat, 23 Jul 2016 20:36:59 -0700, c...@zoffix.com wrote: > Blockless `react` seems to be unsupported and the error message it > throws is cryptic and unrelated to the actual issue. Best would be if > it actually worked, but at least the error message should be improved. > > $ perl6 -e 'react whe

[perl #132093] Enum.succ and Enum.pred are O(n)

On Thu, 14 Sep 2017 18:03:16 -0700, alex.jakime...@gmail.com wrote: > Actually, another direct implication of using .first is this: > > Code: > enum Animal (Cat => 0, Dog => 0, Human => 42); > say Dog.succ > > Result: > Dog > > > So it's not just the algorithmic complexity, and we need a test f

[perl #132093] Enum.succ and Enum.pred are O(n)

On Thu, 14 Sep 2017 18:03:16 -0700, alex.jakime...@gmail.com wrote: > Actually, another direct implication of using .first is this: > > Code: > enum Animal (Cat => 0, Dog => 0, Human => 42); > say Dog.succ > > Result: > Dog > > > So it's not just the algorithmic complexity, and we need a test f

[perl #126842] [BUG] New react + chain syntax locks sometimes

On Tue, 08 Dec 2015 05:40:29 -0800, pub.clau...@gmail.com wrote: > The replacement of the 'whatever' syntax as sugar for consuming Channels > through 'react' locks very often (5-10% of the time). The thread seems to > be stuck on 'shift', probably from the Channel). When rewriting the exact > same

[perl #126842] [BUG] New react + chain syntax locks sometimes

On Tue, 08 Dec 2015 05:40:29 -0800, pub.clau...@gmail.com wrote: > The replacement of the 'whatever' syntax as sugar for consuming Channels > through 'react' locks very often (5-10% of the time). The thread seems to > be stuck on 'shift', probably from the Channel). When rewriting the exact > same

[perl #132091] await handles Slip differently between v6.c and v6.d.PREVIEW

On Thu, 14 Sep 2017 13:30:46 -0700, timo wrote: > I'm using two start blocks that return Slips to generate a long list in > parallel, then i iterate over the result in the Moar Heap Analyzer. > > Trying to take advantage of v6.d's nonblocking await gives me a change > in semantics, though: > >   

[perl #132091] await handles Slip differently between v6.c and v6.d.PREVIEW

On Thu, 14 Sep 2017 13:30:46 -0700, timo wrote: > I'm using two start blocks that return Slips to generate a long list in > parallel, then i iterate over the result in the Moar Heap Analyzer. > > Trying to take advantage of v6.d's nonblocking await gives me a change > in semantics, though: > >   

[perl #130692] [BUG] IO::Socket::Async broken in 6.d.PREVIEW

On Wed, 01 Feb 2017 13:11:21 -0800, j...@gellyfish.co.uk wrote: > With 6.d.PREVIEW the simplest code for IO::Socket::Async mis-behaves: > > use v6.d.PREVIEW; > > react { > whenever IO::Socket::Async.listen('localhost', ) -> $conn { > whenever $conn.Supply(:bin) ->

[perl #130692] [BUG] IO::Socket::Async broken in 6.d.PREVIEW

On Wed, 01 Feb 2017 13:11:21 -0800, j...@gellyfish.co.uk wrote: > With 6.d.PREVIEW the simplest code for IO::Socket::Async mis-behaves: > > use v6.d.PREVIEW; > > react { > whenever IO::Socket::Async.listen('localhost', ) -> $conn { > whenever $conn.Supply(:bin) ->

Re: [perl #132088] [REGRESSION][NATIVECALL] code broken by latest build

I just committed a hotfix so the upcoming release can go through. Hopefully it can be replaced with a proper implementation of optional parameters for the nativecall compiler soon. https://github.com/rakudo/rakudo/commit/1818de980fe39a37b405c0353d088932bd4d034a

Re: [perl #132088] [REGRESSION][NATIVECALL] code broken by latest build

I just committed a hotfix so the upcoming release can go through. Hopefully it can be replaced with a proper implementation of optional parameters for the nativecall compiler soon. https://github.com/rakudo/rakudo/commit/1818de980fe39a37b405c0353d088932bd4d034a

[perl #132093] Enum.succ and Enum.pred are O(n)

On Thu, 14 Sep 2017 17:47:59 -0700, alex.jakime...@gmail.com wrote: > but I guess it is possible to store the index of the current enum value and > simply increment/decrement it when needed. That's trading more RAM for performance increase that's likely inconsequential in nearly all use cases. T

[perl #132093] Enum.succ and Enum.pred are O(n)

On Thu, 14 Sep 2017 17:47:59 -0700, alex.jakime...@gmail.com wrote: > but I guess it is possible to store the index of the current enum value and > simply increment/decrement it when needed. That's trading more RAM for performance increase that's likely inconsequential in nearly all use cases. T