|
00:06
librasteve_ left
00:08
arkiuat joined
00:12
arkiuat left
00:35
arkiuat joined
00:40
arkiuat left
00:50
arkiuat joined
01:24
arkiuat left
01:27
arkiuat joined
01:38
arkiuat left
01:44
arkiuat joined
|
|||
| [Coke] | IMO, not all commits are weekly worthy | 03:52 | |
| [Coke] is looking at, e.g. Merge pull request #6049 from rakudo/release-2025.12 Will Coleda | |||
| If you're going to do a mini changelog each week, I would suggest using the actual in-progress changelog, which gives us a change to a) consolidate or ignore as appropriate, and then b) save that work and re-use it for the actual release. | 03:53 | ||
| librasteve: ^^ | |||
|
06:56
arkiuat left
07:08
arkiuat joined
07:14
arkiuat left
07:44
arkiuat joined
07:50
arkiuat left
08:01
arkiuat joined
08:06
arkiuat left
08:33
arkiuat joined
08:39
arkiuat left
08:43
arkiuat joined
08:47
arkiuat left
|
|||
| disbot7 | <librasteve> [Coke] … thanks for the feedback - I 100% agree. My approach to the weekly so far has been to (i) slavishly follow rakudoweekly.blog/lizs-workflow, (ii) automate the repeated sections and (iii) adjust a little where I think I can improve the content. As far as the Core Developments go, I am at stage (ii) with Liz items 4 and 12. Been a bit time constrained in the last week or two so I am guilty of not manually | 09:02 | |
| weeding these lists, tho tbh I am not very close to the core work. So yes, let’s improve that. | |||
| <librasteve> My preference would be to ask a rep from the core team to write a summary “Core Developments” each week … at least until I have a better window into the priority work streams and how to describe progress in these. In particular (as a non core dev) I feel that I am missing the progress of the main v6e driver … RakuAST. Would you (or someone else) be OK to provide that? | 09:07 | ||
| <librasteve> As an aside on the topic of Raku AST, I sense that the TPRF has some funds available (they just allocated 3500€ for FOSDEM) and I wonder if the “Raku grant application window” is open for new applications? | 09:12 | ||
| <librasteve> PS please can you share a link to the current changelog you mentioned? | 09:13 | ||
|
09:14
donaldh joined
09:16
arkiuat joined,
librasteve_ joined
09:21
arkiuat left
09:50
arkiuat joined
09:55
arkiuat left
10:27
arkiuat joined
10:33
arkiuat left
10:55
arkiuat joined
11:00
arkiuat left
11:10
ShimmerFairy left
11:15
arkiuat joined
11:21
arkiuat left
11:33
arkiuat joined
11:42
arkiuat left
11:49
arkiuat joined
11:53
arkiuat left
12:04
librasteve_ left
12:20
arkiuat joined
12:24
arkiuat left
12:32
arkiuat joined
12:46
arkiuat left
13:02
ShimmerFairy joined
13:06
arkiuat joined
13:11
arkiuat left
13:24
arkiuat joined
13:29
arkiuat left
13:30
librasteve_ joined
13:39
arkiuat joined
13:45
arkiuat left
13:54
arkiuat joined
13:59
arkiuat left
14:24
arkiuat joined
14:31
arkiuat left
14:32
arkiuat joined
14:37
arkiuat left
14:41
arkiuat joined
14:45
arkiuat left
14:52
finanalyst joined
15:07
arkiuat joined
15:12
arkiuat left
15:41
arkiuat joined
15:49
arkiuat left
16:16
finanalyst left
16:18
arkiuat joined
16:23
arkiuat left
16:37
arkiuat joined
17:24
librasteve_ left
18:13
arkiuat left
|
|||
| lizmat | bisectable6: old=2024.02 say (^10).min(:by(-*)) | 18:16 | |
| bisectable6 | lizmat, On both starting points (old=2024.02 new=f95aefa) the exit code is 0 and the output is identical as well | ||
| lizmat, Output on both points: «0» | |||
|
18:16
arkiuat joined
|
|||
| lizmat | bisectable6: old=2022.02 say (^10).min(:by(-*)) | 18:16 | |
| bisectable6 | lizmat, On both starting points (old=2022.02 new=f95aefa) the exit code is 0 and the output is identical as well | ||
| lizmat, Output on both points: «0» | |||
| lizmat | bisectable6: say (^10).min(:by(-*)) | ||
| bisectable6 | lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight | ||
| lizmat, ¦6c (96 commits): «0» | 18:17 | ||
| lizmat, Nothing to bisect! | |||
|
18:21
arkiuat left
18:31
Pixi left
|
|||
| Geth | rakudo/lizmat-Range-minmax-by: 74f3ae1d38 | (Elizabeth Mattijsen)++ | src/core.c/Range.rakumod Add :by support to Range.min/max/minmax Lack of which was spotted in github.com/rakudo/rakudo/issues/6054 |
18:32 | |
| rakudo: lizmat++ created pull request #6055: Add :by support to Range.min/max/minmax |
|||
|
18:39
Pixi joined
18:50
arkiuat joined
18:55
[Tux] left,
arkiuat left
18:58
[Tux] joined
19:23
arkiuat joined
19:28
arkiuat left
19:50
arkiuat joined
19:59
arkiuat left
20:12
arkiuat joined
20:17
arkiuat left
20:36
arkiuat joined
21:18
bisectable6 left
21:22
bisectable6 joined
|
|||