[perl #131395] [BUG] Cross meta operator on empty list complains "This type (Scalar) does not support elems"

2019-05-12 Thread Jan-Olof Hendig via RT
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 ele

[perl #130572] Parenthesized `for` loop is eager, even with `lazy` keyword

2019-05-12 Thread Jan-Olof Hendig via RT
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 https://github.com/rakudo/rakudo/commit/cf1673d9c20e82aad6291a8aa123c46e177ed

[perl #130572] Parenthesized `for` loop is eager, even with `lazy` keyword

2019-05-12 Thread Jan-Olof Hendig via RT
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 > > A

[perl #130069] [BUG] Unknown QAST error when creating List of Pairs

2019-05-12 Thread Jan-Olof Hendig via RT
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 Rat'

[perl #131089] Different parsing of combined colonpairs

2019-05-12 Thread Jan-Olof Hendig via RT
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: -> *@_, *%_ { d

Which TELNET options need to be supported in Net::Telnet?

2019-05-12 Thread Ben Davies
Net::Telnet is just about ready for release v0.0.1 now. Since it's on the most wanted modules list, I figured someone out there needs it and knows how the protocol works. Currently, the library supports the TRANSMIT_BINARY, SGA, ECHO, and NAWS options. I'm planning on gradually adding support f

Re: valid values?

2019-05-12 Thread yary
Side note, using the angle brackets creates IntStr objects, which in some cases is harmless, sometimes necessary. > say <1 2 4 8 16 >.perl (IntStr.new(1, "1"), IntStr.new(2, "2"), IntStr.new(4, "4"), IntStr.new(8, "8"), IntStr.new(16, "16")) > say (1,2,4,8,16).perl (1, 2, 4, 8, 16) That's than

Re: Which TELNET options need to be supported in Net::Telnet?

2019-05-12 Thread yary
Whichever one lets env variables get passed- need to set TERM in particular. -y On Sun, May 12, 2019 at 3:28 PM Ben Davies wrote: > Net::Telnet is just about ready for release v0.0.1 now. Since it's on > the most wanted modules list, I figured someone out there needs it and > knows how the pro

Re: valid values?

2019-05-12 Thread yary
On #perl6 Int(IntStr) will not coerce because IntStr is already an Int; coercions will only fire if the type doesn't match, like with Array and Hash for example IntStr is a subclass of Int thus no coercion needed to set $value. A catch-22 if each right side element is Int as opposed to IntStr, be

Re: valid values?

2019-05-12 Thread yary
"is copy" is what I wanted to allow modifying MAIN's passed-in values. "is rw" correctly rejects constants. sub MAIN(Int $value is copy where ($value .= Int) ∈ (1,2,4,8,16)) {say "\$value.perl = ",$value.perl } # says $value.perl = 4 -y On Sun, May 12, 2019 at 5:02 PM yary wrote: > On #perl6