[perl #132191] [REGRESSION] Possible rakudo regression (issues with IRC::Client)

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132191] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132191 > There is very little known about the problem. I'm creating this ticke

Re: Tip: assign a value to a hash using a variable as a key

On Sat, Sep 30, 2017 at 10:30 PM, ToddAndMargo wrote: > On 09/30/2017 02:15 PM, Brandon Allbery wrote: > >> Basically: < > is single quotes and treats variables and expressions as >> literals. << >> is double quotes and interpolates variables but not general >> expressions. And { } does no quotin

Re: Tip: assign a value to a hash using a variable as a key

On 09/30/2017 02:15 PM, Brandon Allbery wrote: Basically: < > is single quotes and treats variables and expressions as literals. << >> is double quotes and interpolates variables but not general expressions. And { } does no quoting at all and uses general expressions. Hi Brandon, I am writin

Re: Tip: assign a value to a hash using a variable as a key

On Sat, Sep 30, 2017 at 7:44 PM, ToddAndMargo wrote: > On 09/30/2017 02:15 PM, Brandon Allbery wrote: > >> This concept gets reused enough that it's not separately described for >> every place where it is used; the documentation would be impossible to >> manage, almost as impossible to read, and

Re: Tip: assign a value to a hash using a variable as a key

On 09/30/2017 02:15 PM, Brandon Allbery wrote: This concept gets reused enough that it's not separately described for every place where it is used; the documentation would be impossible to manage, almost as impossible to read, and often out of sync with itself if every reused concept had to be

Re: Tip: assign a value to a hash using a variable as a key

On 09/30/2017 02:15 PM, Brandon Allbery wrote: Basically: < > is single quotes and treats variables and expressions as literals. << >> is double quotes and interpolates variables but not general expressions. And { } does no quoting at all and uses general expressions. Thank you!

[perl #132185] [LTA] file tests and Failure do not interact as expected

On Sat, 30 Sep 2017 13:47:22 -0700, allber...@gmail.com wrote: > So I included at least one discussion in the ticket that was utterly > pointless and left unread. At this point I'm just going to assume only > half-exposing the underlying mechanism is considered a feature and I need > to use a diffe

Re: Tip: assign a value to a hash using a variable as a key

On Sat, Sep 30, 2017 at 5:08 PM, ToddAndMargo wrote: > On 09/30/2017 02:20 AM, Timo Paulssen wrote: > >> This doc page should help you a lot with this topic: >> >> https://docs.perl6.org/language/subscripts#Basics >> >> > A little bit. I had found that when I was researching. It did not > go in

Re: Any way to get hashes to loop in order?

On Sat, Sep 30, 2017 at 5:00 PM, ToddAndMargo wrote: > On 09/29/2017 07:25 PM, Brandon Allbery wrote: > >> The point of a hash is that it computes hash values from its keys for >> fast lookup, >> > > Not me. I use them to "organize" data all in one easy to look > up place. For example: > I am

Re: Tip: assign a value to a hash using a variable as a key

On 09/30/2017 02:20 AM, Timo Paulssen wrote: This doc page should help you a lot with this topic: https://docs.perl6.org/language/subscripts#Basics A little bit. I had found that when I was researching. It did not go into who to use a variable as a key value. This is what I wrote myself:

[perl #132183] Insufficient debug messages from zef/perl6.bat when package build fails

# New Ticket Created by Ville Koskinen # Please include the string: [perl #132183] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132183 > I downloaded and installed the latest Windows x64 build of Rakudo (http://rakudo.org/d

[perl #131490] Crash in Junction:D.BUILDALL `This type (Scalar) does not support elems`

On Sat, 30 Sep 2017 13:13:31 -0700, c...@zoffix.com wrote: > Don't see a reason why not. Well, passing a 'type' string parameter to select between what is essentially different object sub-types, seems internal-ish. I can't think of anything else in the public Perl 6 API which does this; a more

Re: Any way to get hashes to loop in order?

On Sep 30, 2017 12:41 PM, "Parrot Raiser" <1parr...@gmail.com > wrote: Prepending the real key value with an order indicator, then sorting the retrieved list on the key would achieve that, (though the maximum number size would have to be known in advance.

Re: Any way to get hashes to loop in order?

On 09/29/2017 07:25 PM, Brandon Allbery wrote: The point of a hash is that it computes hash values from its keys for fast lookup, Not me. I use them to "organize" data all in one easy to look up place. For example: my %SmtpIni = [ 'DebugTrace' => "", 'smtp' => "", 'port'

Re: Any way to get hashes to loop in order?

Maybe a list/array of pairs would be better, and then cast it to a hash if you need to do fast lookups. On Sep 30, 2017 12:41 PM, "Parrot Raiser" <1parr...@gmail.com> wrote: > Prepending the real key value with an order indicator, then sorting > the retrieved list on the key would achieve that, (

Re: [perl #132185] [LTA] file tests and Failure do not interact as expected

On Sat, Sep 30, 2017 at 4:35 PM, Sam S. via RT wrote: > To the extent that you're basing your expectations on the fact that a Perl > 5 `undef` can be used in ways that a Perl 6 `Failure` cannot (without > blowing up), well, that's just a matter of having to unlearn Perl 5 (or > other programming

Re: [perl #132185] [LTA] file tests and Failure do not interact as expected

On Sat, Sep 30, 2017 at 4:35 PM, Sam S. via RT wrote: > To the extent that you're basing your expectations on the fact that a Perl > 5 `undef` can be used in ways that a Perl 6 `Failure` cannot (without > blowing up), well, that's just a matter of having to unlearn Perl 5 (or > other programming

[perl #132185] [LTA] file tests and Failure do not interact as expected

I agree with Zoffix that this seems to be fine as is. Generally speaking, IO operations that logically require an existing path will return a Failure if the path does not in fact exist: Slurp its content? Failure. Rename/move/copy it? Failure. Check its size? Failure. Check if it is of t

[perl #131490] Crash in Junction:D.BUILDALL `This type (Scalar) does not support elems`

On Sat, 30 Sep 2017 12:28:48 -0700, sml...@gmail.com wrote: > Is `Junction.new` meant to be public API? Don't see a reason why not. > If not, do we still need a test for this? If it weren't, all fixed bugs still need a test to cover them. If the test should not become part of the spec, it shoul

[perl #131490] Crash in Junction:D.BUILDALL `This type (Scalar) does not support elems`

On Sat, 30 Sep 2017 12:28:48 -0700, sml...@gmail.com wrote: > Is `Junction.new` meant to be public API? Don't see a reason why not. > If not, do we still need a test for this? If it weren't, all fixed bugs still need a test to cover them. If the test should not become part of the spec, it shoul

Re: Perl 6 Object Construction - General Advice

On Saturday, September 30, Mark Devine wrote: > My most common OC case: initialize attributes at OC time from external > input that will be parsed with grammars &/| scrubbed with elaborate > conditional tests. I like to use assignment for simple things and TWEAK for complicated things -- cl

[perl #125251] Usage does not print required type for positional params in MAIN

I think this bug can be closed. Here's my reasoning. For me, a major point with the auto-generated usage text is that it helps the developer of the program see the importance of picking good variable names. If a dev chooses to name them $integer1 and $integer2 (which are obviously horrible vari

[perl #131395] Using a cross meta operator on an empty list complains about not supporting elems

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 elems". > > > > say (1,2).elems; say ().elems; say (1,2) X (); >

[perl #131490] Crash in Junction:D.BUILDALL `This type (Scalar) does not support elems`

On Fri, 02 Jun 2017 18:58:22 -0700, c...@zoffix.com wrote: > While chasing some other bugs, came across this one: > > m: Junction.new.BUILDALL: {} > rakudo-moar ef9872: OUTPUT: «This type (Scalar) does not > support elems␤ in block at line 1␤␤» > > Not sure how much it matters in itself, but

Re: Any way to get hashes to loop in order?

Prepending the real key value with an order indicator, then sorting the retrieved list on the key would achieve that, (though the maximum number size would have to be known in advance. E.g. 001First_key => data1, 002Second => data2

Perl 6 Object Construction - General Advice

Perl 6, I am preparing to write several classes for some Perl 6 apps I intend to craft in support of a prominent backup suite. In looking at the documentation & some of the modules published in the Perl 6 ecosystem, I’m not quite sure that I can identify the best idiomatic object construction

[perl #132109] [BUG] `.skip` on a sequence starting with a `Slip`, returns a corrupted `Seq`

On Sat, 16 Sep 2017 22:29:57 -0700, sml...@gmail.com wrote: > When calling `.skip` on a list which contains a `Slip` at the start, the > resulting `Seq` behaves in some cases as if *all* elements from that > `Slip` were skipped (instead of just the first one): > > say (, ).map(|*).skip.perl

[perl #132109] [BUG] `.skip` on a sequence starting with a `Slip`, returns a corrupted `Seq`

On Sat, 16 Sep 2017 22:29:57 -0700, sml...@gmail.com wrote: > When calling `.skip` on a list which contains a `Slip` at the start, the > resulting `Seq` behaves in some cases as if *all* elements from that > `Slip` were skipped (instead of just the first one): > > say (, ).map(|*).skip.perl

Re: Tip: assign a value to a hash using a variable as a key

This doc page should help you a lot with this topic: https://docs.perl6.org/language/subscripts#Basics

Tip: assign a value to a hash using a variable as a key

Hi All, This one about killed me to find! The guys on the chat line figured it out for me. Apparently some tutorial is wrong on this too, but I couldn't figure out which one they were referring to. When assigning a value to a hash using a variable as the key, use {} instead of <> perl6 -e '