AlexDaniel oh, there's also Sequence and HyperSeq/RaceSeq 00:00
at least that's what the docssay 00:01
docs say*
jnthn Sure
AlexDaniel
.oO( Tonight on Raku FM: AlexDaniel learns the basics of Raku… )
 00:03
jnthn :)
To be fair, for the range of functionality being made available, I don't think we're doing any worse than other languages whose standard library (or libraries that may as well be) provide the same. 00:06
Xliff
.oO( This is a silly radio show. I thought those were the same basics as Perl6! )
 00:07
Please pardon the impending snark... I am dealing with Bluehost support for $dayjob and they are giving me the runaround.
AlexDaniel jnthn: hypothetically, what if Seq and List were the same thing? 00:08
jnthn I think it maybe just surprises folks a bit more in Raku to discover them all, because one just does `@foo.race.map(*.blah)` and doesn't even thing that much about the types involved.
AlexDaniel: Memory leaks all over :)
AlexDaniel jnthn: I mean, what if List was Seq? :)
jnthn I know because *we used to have it that way*!
tbrowder jnthn: lizmat has asked for yr review of my PR 3310 when you get a chance. it implements log2 routine. 00:09
tellable6 2019-11-29T08:26:21Z #raku <jmerelo> tbrowder great job!
jnthn If List was Seq...I dunno how one'd achieve that, given Seq uses List as part of its cache implementation
Xliff Memory leaks? How about brain leaks?!
Mine are coming out my ear... 00:10
jnthn It may be possible, but I'm not sure how practical it is
AlexDaniel okay 00:12
Geth rakudo: vrurg++ created pull request #3332:
Change the way compiler version is chosen for COREs		 02:15
vrurg Appveyor is seemingly broken, can't fetch strawberry perl. 02:27
lizmat Files=1290, Tests=109646, 206 wallclock secs (28.00 usr 7.78 sys + 2915.84 cusr 261.47 csys = 3213.09 CPU) 10:12
re Dict / Tuple discussion last night: We need value types for Associative and Positional roles. We need these so that they can be used in QuantHashes and object hashes. I do not care what they are called. 10:23
ValueMap / ValueList would be fine for me as well 10:27
Geth ¦ problem-solving: lizmat assigned to jnthn Issue How to provide coercers for new types in higher language versions github.com/perl6/problem-solving/issues/137 10:47
lizmat provided 3 possible solutions, hope there'll be more soon 11:02
Geth rakudo/add-Dict: 8a857c06ce | (Elizabeth Mattijsen)++ | src/core.e/Dict.pm6
Fix STORE signature
 11:25
Geth rakudo/add-Dict: a068fb4853 | (Elizabeth Mattijsen)++ | 2 files
Add a 6.e core epilogue that recomposes selected classes

To make sure that the .Dict coercer becomes visible to the classes it will most likely be called upon.		 12:17
rakudo/add-Dict: d9123603fd | (Elizabeth Mattijsen)++ | src/core.e/core_epilogue.pm6
Re-compose some more classes, also Positionals
sena_kun ok, this is ridiculous, `curl -v -s www.perlfoundation.org/contributor...ment.html` says `connect to 64:ff9b::c722:e44a port 80 failed: Network is unreachable` and disconnects. 12:29
can anyone help me with obtaining the file?
nine sena_kun: try curl -4 12:33
sena_kun tries out 12:34
gist.github.com/Altai-man/be7037af...e58c342c69 12:38
nine sena_kun: niner.name/files/contributor-licens...ement.html 12:43
sena_kun nine, thanks!
lizmat .tell [Coke] looks like www.perlfoundation.org/contributor...ement.html is dead 14:41
tellable6 lizmat, I'll pass your message to [Coke]
Geth rakudo/add-Dict: b9d2327b2a | (Elizabeth Mattijsen)++ | src/core.e/core_epilogue.pm6
Revert "Re-compose some more classes, also Positionals"

This reverts commit d9123603fd58a11947d2913e8bb0c956d6c62705.		 15:35
rakudo/add-Dict: 788143aab8 | (Elizabeth Mattijsen)++ | 2 files
Revert "Add a 6.e core epilogue that recomposes selected classes"

This reverts commit a068fb4853531e9c8d41126c8a86d9bfaf4feba5.
Geth rakudo: 1d8d62d46d | (Elizabeth Mattijsen)++ | src/core.c/core_epilogue.pm6
Revert the temporary fix of R#2640

Looks like the problem has since gone away. Please revert back should this be false.		 16:07
lizmat .tell SmokeMachine could you please check that Red survived github.com/rakudo/rakudo/commit/1d8d62d46d ?
tellable6 lizmat, I'll pass your message to SmokeMachine
Geth problem-solving/CoC: 594c2e0403 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Remove double negation:

So it becomes:
   We discriminate on the ability to be a kind, positive member of our community		 17:39
problem-solving/CoC: 37204bc9eb | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Elaborate on standards of behavior
 17:43
problem-solving/CoC: 099419cacd | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Removed the "aside about trolls" paragraph

This indeed appears to be written in an era where trolls really were a major issue for Raku. After the change of name to Raku, this appears to be a lot less the case. So no reason to actually emphasize something that is quickly becoming a historical artefact.		 17:48
Xliff \o 17:49
What's the difference between ParametricRoleHOW and ParametricRoleGroupHOW?
Geth problem-solving/CoC: dff95308b8 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Remove the quip about high level language

It feels very Perlish / TimToady-like. And hard to understand if you do not know the background of Raku and its long gestation process.		 17:52
problem-solving/CoC: d7d4656206 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
We **only** discriminate, japhb++
 17:57
problem-solving/CoC: 434311f73b | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Mention effect on karma, rather than a possible reason

  japhb++ again.		 18:04
vrurg Xliff: Role group is a group of individual parametric roles. 18:08
Geth rakudo: 4e9487ce2a | (Vadim Belman)++ | 3 files
Change the way compiler version is chosen for COREs

Compiling a CORE with version lower than default can cause performance degradation because not all current optimizations would be used. Thus, the previous decision of compiling each core with corresponding compiler considered erroneous.
... (11 more lines)		 18:11
rakudo: b4fb30889f | (Vadim Belman)++ (committed using GitHub Web editor) | 3 files
Merge pull request #3332 from vrurg/rakudo_3326

Change the way compiler version is chosen for COREs
problem-solving/CoC: f2b2694635 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Added section about good intentions and arbitration
 18:41
Xliff vrurg: OK. But it's being applied to a single role. So I guess a group can be 1, yes? 18:42
lizmat Xliff: I think so 18:43
it's easier on the compiler logic, because during parsing you don't know how many roles you're going to encounter 18:44
so you always start with a group
Xliff COK 18:45
s/C//
Xliff OK, now here's the current problem. Previously roles would return ParametricRoleHow both as $*PACKAGE and then when referred to by name. 20:30
Now $*PACKAGE is still ParametricRoleHOW, but the role by name is now ParametricRoleGroupHOW. 20:31
This breaks things down the line.
What's the best way to resolve? Preferably given the ability to pun roles on ParametricRoleGroupHOW when given the ParametricRoleHOW?
vrurg Xliff: I don't understand what you're trying to achieve 20:33
And a role by name was always a group. 20:35
Xliff Well, something recent changed with roles because Method::Also isn't working when attaching aliases via role. 20:46
Right now, I can't figure out why. 20:47
Right now I am attaching aliases to a class with roles via specialize and specialize-with 20:48
And they are not getting picked up.
They were, last week.
Or maybe the week before. Kinda hard to tell. I have lots of projects, now.
Geth problem-solving/CoC: f315ca777f | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Define a troll as a person lacking of good intentions
 21:07
lizmat Xliff: are the projects that are failing now in the ecosystem? iow, should Blin have picked up the breakage ? 21:08
vrurg Blin could've skipped it if the case isn't covered by a test. 21:16
Geth problem-solving/CoC: 21c86e1f35 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
First stab at a "Responsibility" section

Definitely *not* happy with the wording yet. Throwing it out there for feedback.
Xliff lizmat: No. None of this is in the ecosystem, so Blin would not have detected them. 21:47
lizmat :-(
vrurg Xliff: it wouldn't anyway because it passess tests. 21:57
Xliff: so, it needs a test for the breakage. 21:58
japhb lizmat: I've added comments on 2 out of your last 3 commits. 21:59
Xliff vrurg: OK, the culprit is easy. The aliases in the roles are not getting composed. 22:24
And at least from what I can see, this means that AliasableRoleHOW.specialize is not being called at all. 22:25
I know all of the defined role HOWs are being punned with it, so what would cause that to not execute? 22:26
jnthn Xliff: fwiw, I don't think there's - for probbly close to a decade - been a time when a role name didn't evaluate to a ParametricRoleGroupHOW 22:31
Xliff jnthn: Thanks for that. It means my initial suspicion was incorrect. However this code worked as recently as 2 weeks ago and it hasn't changed. I've already had to fix something in it once due to a weird change. 22:37
I just want to localize what broke things and fix it.
Geth rakudo: f6254be1ae | (Tom Browder)++ | 9 files
Implement log2 function
 23:12
rakudo: c16b5a204f | (Tom Browder)++ (committed using GitHub Web editor) | 9 files
Merge pull request #3310 from tbrowder/log2

Implement log2 function
Xliff When is .specialize called on a ParametricRoleHOW? 23:52
And how does ParametricRoleHOW fit in with ParametricRoleGroupHOW? 23:53

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!