Re: Associative collection with automatic keys?

On Wed, Apr 05, 2017 at 01:33:58AM +0200, Elizabeth Mattijsen wrote: > > On 4 Apr 2017, at 11:31, Trey Ethan Harris wrote: > > > > I'm thinking of a Hash-like collection where I can add objects using a > > index-less append operation, but then have random access to the elements > > based on a k

[perl #131102] [REGRESSION] anonymous variables are no longer working as expected in regex code blocks

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #131102] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131102 > Code: (^10).grep: /^ / Result (2015.12,2016.10): 0 1 2 3 4 5 6 7 8

Re: Associative collection with automatic keys?

> On 4 Apr 2017, at 11:31, Trey Ethan Harris wrote: > > I'm thinking of a Hash-like collection where I can add objects using a > index-less append operation, but then have random access to the elements > based on a key provided by the object. (For instance, imagine a ProcessTable, > where I cr

Associative collection with automatic keys?

I'm thinking of a Hash-like collection where I can add objects using a index-less append operation, but then have random access to the elements based on a key provided by the object. (For instance, imagine a ProcessTable, where I create the collection telling it to index by the .pid method, add eac

[perl #131099] [LTA] is assoc('list') gives "MVMArray: Can't pop from an empty array"

On Tue, 04 Apr 2017 11:05:05 -0700, c...@zoffix.com wrote: > On prefix and postfix ops, using `is assoc('list')` causes an LTA > error without any location. > > I've no idea if it makes sense for them to be assoc list; originally, > I came across this while trying to make a postfix op `is > equiv(

[perl #131099] [LTA] is assoc('list') gives "MVMArray: Can't pop from an empty array"

# New Ticket Created by Zoffix Znet # Please include the string: [perl #131099] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131099 > On prefix and postfix ops, using `is assoc('list')` causes an LTA error without any locat

[perl #130857] WARNING: unhandled Failure detected in DESTROY

I only now realized what this message actually means /o\ A Failure that neither exploded nor was handled got GCed, potentially indicating an error in user's code due to missed Failures. I improved the message in https://github.com/rakudo/rakudo/commit/75c3f29100

[perl #131092] [REGEX] Alternation fails matching the same token on either side

On Sun, 02 Apr 2017 19:19:11 -0700, lloyd.fo...@gmail.com wrote: > use Grammar::Tracer; > grammar G { > token TOP { || } > token first-fail { '?' } > token second-succeed { '!' } > token thing { "foo" } > } > note G.parse("foo!") > > #grammar tracer output: > > TOP > | first-

[perl #131097] Why doesn't Perl 6's try handle a non-zero exit in shell()?

On Tue, 04 Apr 2017 02:52:53 -0700, comdog wrote: > I originally asked about this on Stackoverflow > (http://stackoverflow.com/q/43199427/2766176) > > This `try` catches the exception: > > try die X::AdHoc; > say "Got to the end"; > > The output shows that the program continues: > > Got to the

Re: [perl #131097] Why doesn't Perl 6's try handle a non-zero exit in shell()?

Thanks for reporting! Turns out this isn’t actually a bug, but the way shell() works. As Jonathan explained at: https://irclog.perlgeek.de/perl6-dev/2017-04-04#i_14372945 the shell() function returns a Proc object. This only throws the shelling out failed and the Proc object is sunk. So E

[perl #131097] Why doesn't Perl 6's try handle a non-zero exit in shell()?

# New Ticket Created by "brian d foy" # Please include the string: [perl #131097] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131097 > I originally asked about this on Stackoverflow (http://stackoverflow.com/q/43199427/2766