Re: Who's who of the ecosystem?

For general language problems there is special repo on github where one can raise a matter: https://github.com/perl6/problem-solving . Note though it's not a bug-reporting resource, but more information about it's purpose can be found in repo's README.

Re: Rakudo Star 2019.07.1

Ah, that has been a mistake on my part, apologies. I can use a more "correct" naming scheme in the future. Are there any rules besides this one that release names should adhere to? I'll write up a document about it so I have it documented, and other people know what to expect as well. On Wed, 6

Who's who of the ecosystem?

Raku is the product of collaboration by many people. Some of these are well known, but there are many parts of the ecosystem whose mavens are anonymous or obscure. When a problem arises, it would be nice to be able to direct them to someone knowledgeable, rather than essentially yelling them in

Re: Rakudo Star 2019.07.1

This is not really zef's "implementation detail". See rakudo sources in src/core.c/CompUnit and grep for 'sha1'. Best regards, Vadim Belman > On Nov 6, 2019, at 9:04 AM, Patrick Spek via perl6-users > wrote: > > The problem is clearly with the Linenoise module, I'll have to look > into that

Re: Rakudo Star 2019.07.1

When I report a problem, I try to supply as complete a picture as possible, without imposing my filter on the data. So many times I've had a vital clue omitted by someone who "didn't think that X was important". With so many parties involved, it's not surprising that errors reveal issues entirely

Re: Rakudo Star 2019.07.1

The problem is clearly with the Linenoise module, I'll have to look into that and see if it's something I can fix. The path name you see is "an implementation detail" of Zef, I've been told before. I have no clue how it actually calculates them, and no idea where to find any documentation on