|
🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm Set by lizmat on 8 June 2022. |
|||
|
00:00
reportable6 left
00:01
reportable6 joined
|
|||
| Geth | rakudo: vrurg++ created pull request #5174: Try to be more explicit when exception reporting dies |
00:23 | |
|
01:59
bloatable6 left,
coverable6 left,
evalable6 left,
reportable6 left,
greppable6 left,
notable6 left,
releasable6 left,
shareable6 left,
unicodable6 left,
committable6 left,
linkable6 left,
sourceable6 left,
quotable6 left,
squashable6 left,
tellable6 left,
nativecallable6 left,
statisfiable6 left,
benchable6 left,
bisectable6 left
02:00
tellable6 joined,
reportable6 joined,
releasable6 joined,
shareable6 joined,
bloatable6 joined,
greppable6 joined,
coverable6 joined,
sourceable6 joined,
notable6 joined,
evalable6 joined
02:01
statisfiable6 joined,
squashable6 joined,
benchable6 joined,
quotable6 joined
02:02
unicodable6 joined,
committable6 joined,
bisectable6 joined,
nativecallable6 joined,
linkable6 joined
03:26
raschip left
05:02
dogbert11 joined
05:05
dogbert17 left
06:00
reportable6 left
06:01
reportable6 joined
07:18
guifa left
07:19
guifa joined
07:43
sena_kun joined
|
|||
| nine | say $_ if $_ %% 2 for 1..10 # this is a hard one | 08:45 | |
| evalable6 | 2 4 6 8 10 |
||
| nine | The if here is a statement modifier. It wraps the statement's expression in an nqp::if with appropriate return values. The for is also a statement modifier. It thunks the expression and wraps that with appropriate looping code. | 08:46 | |
| The problem is when we have both of them on a statement like in this example. Then the nqp::if wrapper would have to go on the expression, i.e. it must be part of the thunk. Currently instead it wraps the calling of the thunk. This is a problem because a for loop is just a call to .map on the list. This map gets passed the thunk to run. Currently instead we evaluate the nqp::if and pass the result to the | 08:48 | ||
| Nemokosch | This definitely had bugs | ||
| nine | map which gets totally confused. | ||
| Nemokosch | With for + with, I think it was bugged | 08:49 | |
|
10:25
Altai-man joined
10:27
sena_kun left
10:31
Altai-man left
11:06
sena_kun joined
|
|||
| Geth | rakudo/main: 95f6c5b4e9 | (Stefan Seifert)++ | 2 files RakuAST: fix miscompilation of statements with both condition and loop modifiers Postfix conditions are statement modifiers. They wraps the statement's expression in the appropriate op (e.g. nqp::if) with appropriate return values. A postfix for is also a statement modifier. It thunks the expression and wraps that with appropriate looping code. The problem was when we had both of them on a statement. Then the condition wrapper would have to go on the expression, ... (15 more lines) |
11:47 | |
| nine | This brings us to 121 test and 652 spectest files! | 11:48 | |
|
11:57
raschip joined
12:00
reportable6 left
12:01
reportable6 joined,
samcv joined,
samcv_ left
12:02
sivoais left
12:03
sivoais joined
|
|||
| Geth | rakudo/main: c3155c0558 | (Stefan Seifert)++ | src/Raku/Actions.nqp RakuAST: fix regex definitions not finding their package |
12:44 | |
| nine | 658 spectests! Confirming that there is still a lot of low hanging fruit | ||
|
12:52
raschip left
13:03
raschip joined
|
|||
| Geth | rakudo/main: 349b1a8306 | (Stefan Seifert)++ | src/Raku/Actions.nqp RakuAST: fix reporting of POD variable NYI errors We didn't make it far enough through compilation to even report the sorry, so just die instead. It's only there until everything's implemented anyway. |
13:04 | |
| releasable6 | Next release in ≈4 days and ≈3 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft | 15:00 | |
|
15:37
NemokoschKiwi joined
15:38
NemokoschKiwi left
|
|||
| Geth | rakudo/main: 45b1978422 | (Vadim Belman)++ | src/core.c/Exception.pm6 Try to be more explicit when exception reporting dies Currently when this happens at compile time we end up with useless 'No exception handler found for catch' message providing us with no information as to what the original cause was. With this commit we would try to pull out as much info as possible at report it back with no bells and whistles. |
16:09 | |
| rakudo/main: d5a839672b | (Vadim Belman)++ (committed using GitHub Web editor) | src/core.c/Exception.pm6 Merge pull request #5174 from vrurg/detailed-runaway-exception Try to be more explicit when exception reporting dies |
|||
|
17:19
sena_kun left
17:53
sena_kun joined
18:00
reportable6 left,
reportable6 joined
20:52
epony left
20:57
raschip left
21:17
epony joined
|
|||
| Geth | rakudo/main: 97a68d10a7 | (Stefan Seifert)++ | 2 files RakuAST: make SETTING:: actually find the setting !UNIT_MARKER was missing and Pseudostash needed adjusting because RakuAST compiled comp units don't have the outer-unit frame. |
21:29 | |
| nine | And that's 125 passing test files :) | 21:30 | |
| vrurg | nine: !!! | 22:04 | |
|
22:15
japhb joined
23:07
Voldenet_ joined
23:09
Voldenet left,
Voldenet_ is now known as Voldenet
23:29
sena_kun left
|
|||