jdv79 anyone know who runs colabti.org? the logger seems to have been downe for a while. 04:03
05:24 Xliff joined 06:20 frost-lab joined 06:21 Xliff left 07:22 evalable6 joined 07:23 linkable6 joined 07:29 jmerelo joined 08:16 sena_kun joined 09:05 JRaspass joined
sena_kun ===> Fetching [FAIL]: WWW:ver<1.005004>:auth<github:perl6-community-modules> from github.com/perl6-community-modules/WWW.git 09:37
What's curious is that it works locally, likely due to a local cache. Can anyone try `zef install WWW`?
I assume github.com/raku-community-modules/...6.json#L24 should be changed and then re-indexed by the ecosystem? 09:38
jmerelo sena_kun: it probably should. I don't want to do it before solving issues, however 09:39
sena_kun: that shouldn't be a problem, however, unless redirections no longer work. 09:40
sena_kun: anyway, as I say, better solve outstanding issues before re-releasing it. 09:42
sena_kun jmerelo, before solving what issues? Redirects should work, yes, but I am still seeing the error for the third time, so apparently they don't somewhere.
jmerelo sena_kun: well, there are a few of them github.com/raku-community-modules/WWW/issues 09:46
sena_kun jmerelo, github.com/raku-community-modules/WWW/issues/19 <- one of the issues is literally what I have right now. And it is probably caused by a redirect not working.
No? 09:47
jmerelo sena_kun: the comment states that there's some issue with authentication. So we'll need to fix the tests (or the underlying code, or both). 09:48
My point is that it's not worth the while to change the link in META.list in the ecosystem and/or the META6.json link (which seems to have been fixed by lizmat, BTW), without looking at that other issues that might make it fail anyway
sena_kun jmerelo, I think this is a fallback behavior due to issues with fetching. 09:49
jmerelo, no, it is worth. There was a module. People relied on that, other modules relied on that. Now fetching is broken due to a link being changed. And you are saying we should not fix fetching, because there are some other issues that might be irrelevant, wishlist ones, etc? 09:50
I am not getting it.
Not sure if a version bump is necessary. 09:56
jmerelo sena_kun: let me work on that this morning. And yes, a version bump is necessary. 10:08
sena_kun jmerelo, I already did github.com/raku-community-modules/...eb30edff47 10:09
10:14 leont joined
jmerelo sena_kun: thanks. I'm still trying to fix a few things... Also need to test if that effectively solves issue #19 10:26
10:56 |Tux| joined 10:57 Tux__ joined, |Tux| left 10:58 Tux__ left 10:59 Tux__ joined 11:00 Tux__ left, Tux__ joined 11:03 Tux__ left 11:12 squashable6 joined 11:57 Altai-man joined 12:00 sena_kun left 12:38 frost-lab left 14:01 jmerelo left 14:45 zostay joined 14:47 rypervenche joined, epony joined
timotimo i have no reason for wanting this, but it randomly occurs to me that when you return something from .^parameterize that also has a .^parameterize you can have types be like MyType[foo][bar][baz] 15:03
15:25 maggotbrain left 15:26 vrurg_ joined 15:27 maggotbrain joined 15:29 vrurg left 15:37 kanopis joined, kanopis left 15:38 kanopis joined
Geth rakudo: 8a3e983c99 | (Elizabeth Mattijsen)++ | 2 files
Throw on non-Int result in Iterable index on native array

Because slices on native arrays return the same type of array on which the slice is based, it cannot represent nested indexes like:
   @a[1,2,(3,4)]
   @a[1,2,*]
... (5 more lines)		 15:46
15:59 sena_kun joined, Altai-man left
Geth rakudo: 5eb5507640 | (Elizabeth Mattijsen)++ | 2 files
Throw on non-Int result in Iterable index on native array assignment

See previous commit for rationale		 16:20
16:30 kanopis left 16:40 patrickb joined 16:46 patrickb left
Geth rakudo: 4d40e23e0f | (Elizabeth Mattijsen)++ | 2 files
Add candidate for native slice assignment from Iterable

Makes slice assignment on a native array from an Iterable about 15x as fast. Also makes it more correct:
If the values for a slice assignment to a native array are not of the same type, it would fall back to the generic slice assignment. This would a. return a List rather than a native array of the same type, and b. would not die on passing nested indices like with other slices on native arrays.		 17:03
MasterDuke lizmat: just curious, do you get a noticeably longer stage parse on the faster-slice-access branch? 17:05
lizmat MasterDuke: yes, because there is a lot more code to parse 17:06
MasterDuke yeah, i wondered if it was enough to make a difference 17:07
17:07 leont left
lizmat 79603 vs 73339 lines in gen/moar/CORE.c.setting 17:08
17:17 Kaiepi left 17:43 domidumont joined 18:13 Kaiepi joined 18:16 domidumont left 18:19 ggoebel joined 19:13 leont joined 19:57 Altai-man joined 20:00 sena_kun left 20:06 tobs joined 20:11 tobs left 20:14 tobs joined 20:18 tobs left 20:21 tobs joined
timotimo wow 20:29
that's a lot of code right there
lizmat yes 20:52
20:52 b2gills left
lizmat that's only to get around the performance issue of a role calling a private method in a consuming class 20:53
fwiw, this only creates more code
if it had been generated as roles and consuming classes, it would still codegen the same amount of code 20:54
would it not?
so the binary size would be the same whether they'd come from generated code like this, or codegenned code from roles and classes 20:55
the only disadvantage, as MasterDuke noted, is increased core setting compilation time 20:56
21:00 tobs left 21:06 tobs joined 21:09 ggoebel left 21:11 tobs left 21:15 ggoebel joined 21:20 tobs joined 21:22 rypervenche left 21:23 b2gills joined 21:24 sortiz joined 21:25 rypervenche joined
sortiz Trying to address an issue on Window 10, I find many failures at rakudo's test time. Details in gist.github.com/salortiz/7934a39b7...6fa8f23c71 21:45
I've been out of the loop for many months. Are those glitches expected in Windows? 21:56
Geth problem-solving/solution-250: 5637dc6f8d | Altai-man++ | solutions/documentation/search-categories.md
Provide a solution document for github.com/Raku/problem-solving/issues/250

  "Documentation search categories are not standartized"
Fixes github.com/Raku/problem-solving/issues/250		 22:01
problem-solving: Altai-man++ created pull request #256:
Provide a solution document for #250		 22:02
nine sortiz: no? 22:07
tellable6 2021-01-04T18:40:06Z #moarvm <brrt> nine it may be worth having a MVM_VECTOR_PARAM(x) macro that specifies the vector as a parameter, and maybe an equivalent MVM_VECTOR_ARG(x) that does the same for arguments
22:07 Altai-man left 22:38 finsternis joined

Powered by Cro and the Raku® Programming Language.

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

Thank you!