|
01:06
vrurg_ joined
01:07
vrurg__ joined
01:09
vrurg left
01:12
vrurg_ left
02:35
vrurg joined
02:38
vrurg__ left
05:15
bloatable6 left,
tellable6 left
06:21
linkable6 left,
linkable6 joined
06:58
ab5tract left
07:01
ab5tract joined
08:58
librasteve_ joined
09:12
rakkable left,
nine left,
unicodable6 left,
benchable6 left
09:14
rakkable joined,
nine joined,
unicodable6 joined,
benchable6 joined
|
|||
| librasteve_ | rakudoweekly.blog/2025/10/06/2025-...dem-calls/ | 09:20 | |
| lizmat | librasteve_++ | 09:26 | |
|
10:30
samebchase left,
djinni`_ left
10:31
samebchase joined,
notable6 left,
notable6 joined
|
|||
| Geth | rakudo: ab5tract self-assigned Occurrences of `$*W` in the core will break in 6.e release github.com/rakudo/rakudo/issues/5324 ab5tract++ created pull request #5969: RakuAST - Remove special handling of '$]' |
10:33 | |
|
10:34
JRaspass left,
JRaspass joined
|
|||
|
10:35
djinni` joined
|
|||
| Geth | rakudo/main: 21dd9921de | ab5tract++ | src/Raku/Grammar.nqp RakuAST - Remove special handling of '$]' This commit addresses R#5652 (#5652), which noted the following malfunction: using a state variable inside of a positional lookup, eg. `[++$]` caused a SORRY exception related to informing the user of differences between Perl and Raku. ... (6 more lines) |
11:27 | |
| linkable6 | R#5652 [open]: github.com/rakudo/rakudo/issues/5652 [Will be addressed in RakuAST] Can the parser for $] be made a little less agressive? | ||
| [Coke] | I believe the "new pull requests" section is only showing open PRs since the last week, yes? | 11:51 | |
| Do we also want to show those were opened and already applied? | |||
| librasteve_: ^^ and the links to the problem-solving tickets are reversed from the order of the text (shows A B C, but they link to C B A) | 12:24 | ||
| ab5tract | [Coke]++ for the proofreading | 12:48 | |
| m: role R[::T] { my package G { class A is Array[T] {}; }; method a { G::A } }; my class CStr does R[Str] { }; dd :a(CStr.a) | |||
| camelia | :a(R::G::A[Str]) | ||
| ab5tract | nine: am I crazy or should that actually be `R[Int[G::A` ? | 12:49 | |
| `R[Int]::G::A` | |||
| (sorry, switched from `Int` to `Str` when typing in the example. the difference of type is of no consequence to my question) | 12:51 | ||
| librasteve_ | Coke: I chose to place the PRs in time order. Can’t guarantee that I’ll remember that every week. Please treat this as a pseudo random order with no preferential intent. | 12:59 | |
| Coke: on the PRs applied vs new PRs I have been naively following the Liz’s process page on the weekly website … next week, I’ll engage my brain and try to give a better insight. Really I could use a bit more engagement to the core work to do a proper reflection of all the core (and doc) dev work … so I’ll aim to improve this. Any suggestions very welcome! | 13:04 | ||
| [Coke] | the A B C vs. C B A - the actual links are wrong - you click on A you get C | 13:13 | |
|
14:07
melezhik joined
|
|||
| [Coke] | ... ok, either you fixed that, or I was hallucinating the error. Thanks! | 14:13 | |
|
15:47
vrurg_ joined
15:48
melezhik_ joined
15:51
melezhik_ left,
vrurg left
15:52
vrurg joined
15:55
vrurg_ left
|
|||
| [Coke] | thoughts on whether we have enough commits to make a release worth it this month? | 16:58 | |
| librasteve_: what's the URL to the process? | 16:59 | ||
| lizmat | I think ab5tract has made some significant fixes | 17:03 | |
| [Coke] | excellent. | 17:19 | |
| I'm on the hook for the release this month. ISTR there was a blin blocker as well (compilable was stuck) but I think we're good there now. | 17:20 | ||
| c: 21dd9921d 3.put | |||
| committable6 | [Coke], ¦21dd992: «Cannot test this commit (Commit exists, but an executable could not be built for it)» | ||
| [Coke] | uhoh | 17:21 | |
| c: 7192f67af 2.put | |||
| committable6 | [Coke], ¦7192f67: «2» | ||
| [Coke] | c: f6180a311 1.put | ||
| committable6 | [Coke], ¦f6180a3: «1» | ||
| [Coke] | ok, so just the most recent commit has an issue | ||
|
17:28
librasteve_ left
18:04
melezhik left
|
|||
| [Coke] | c: 21dd9921d 3.put # on a delay? | 18:44 | |
| committable6 | [Coke], ¦21dd992: «Cannot test this commit (Commit exists, but an executable could not be built for it)» | ||
| [Coke] wonders if there's a way to see the build log for that | |||
|
18:47
Geth left,
Geth joined,
apogee_ntv left,
lucs left,
camelia left
18:48
apogee_ntv joined
18:49
lucs joined
18:51
camelia joined
|
|||
| [Coke] | that commit seems to build fine here. | 18:51 | |
|
21:09
finanalyst joined
21:14
finanalyst left
|
|||