|
🦋 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: ... | log inspection situation still under development | For MoarVM see #moarvm Set by lizmat on 22 May 2021. |
|||
|
00:05
reportable6 left,
reportable6 joined
01:51
linkable6 left,
sourceable6 left,
reportable6 left,
quotable6 left,
benchable6 left,
unicodable6 left,
greppable6 left,
bloatable6 left,
coverable6 left,
committable6 left,
bisectable6 left,
shareable6 left,
evalable6 left,
releasable6 left,
statisfiable6 left,
nativecallable6 left,
notable6 left,
committable6 joined,
shareable6 joined
01:52
releasable6 joined,
bloatable6 joined,
statisfiable6 joined,
evalable6 joined
01:53
linkable6 joined,
bisectable6 joined,
benchable6 joined,
reportable6 joined,
unicodable6 joined,
notable6 joined,
coverable6 joined,
quotable6 joined
01:54
greppable6 joined,
nativecallable6 joined,
sourceable6 joined
02:13
ggoebel joined
02:20
ggoebel_ joined,
ggoebel left
02:26
ggoebel_ left
04:06
nativecallable6 left,
reportable6 left,
coverable6 left,
notable6 left,
quotable6 left,
greppable6 left,
bloatable6 left,
shareable6 left,
releasable6 left,
evalable6 left,
benchable6 left,
bisectable6 left,
unicodable6 left,
sourceable6 left,
statisfiable6 left,
linkable6 left,
committable6 left,
evalable6 joined
04:07
shareable6 joined,
committable6 joined,
coverable6 joined,
statisfiable6 joined
04:08
notable6 joined,
greppable6 joined,
reportable6 joined,
benchable6 joined,
unicodable6 joined,
nativecallable6 joined,
linkable6 joined,
sourceable6 joined,
bloatable6 joined,
releasable6 joined,
quotable6 joined
04:09
bisectable6 joined
05:39
evalable6 left,
linkable6 left,
linkable6 joined
05:40
evalable6 joined
06:07
reportable6 left
06:08
reportable6 joined
06:39
Geth left,
moon-child left,
tbrowder left,
zostay left,
Geth joined,
tbrowder joined,
moon-child joined,
zostay joined
06:43
samebchase left
07:49
sena_kun left
07:58
sena_kun joined
|
|||
| lizmat | Files=1352, Tests=117130, 288 wallclock secs (35.34 usr 9.75 sys + 4027.05 cusr 323.72 csys = 4395.86 CPU) | 08:49 | |
|
08:58
linkable6 left,
evalable6 left
08:59
linkable6 joined
09:00
evalable6 joined
09:36
Xliff joined
10:36
Altai-man joined
|
|||
| lizmat | notable6: weekly | 11:35 | |
| notable6 | lizmat, No notes for “weekly” | ||
|
12:07
reportable6 left
12:09
reportable6 joined
|
|||
| lizmat | and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2022/04/04/2022-...completer/ | 12:45 | |
| [Coke] | www.securityweek.com/checkmarx-fin...in-attacks | 12:49 | |
| Forcing the authors to be registered elsewhere helps; does our new system deal with this kind of attack where someone is creating multiple auths? | 12:51 | ||
| lizmat | I guess the zef ecosystem links an auth to an email address | 12:58 | |
| and that's about it | |||
| and technically, someone could upload a module "Foo" with a higher version than any "Foo" that's in there already | 12:59 | ||
| the only way to make sure you get a correct version of your module in your code, is to at least also specify an "auth" in your use statement | 13:00 | ||
| having said that, so far that hasn't been necessary, but then again, it's still early in Raku's life cycle | |||
|
13:09
linkable6 left,
evalable6 left
13:12
linkable6 joined,
evalable6 joined
|
|||
| [Coke] | Sounds like that's a reasonable answer though: that we can trust/require an existing author. | 13:22 | |
|
13:40
Altai-man left,
Altai-man joined
15:04
discord-raku-bot left
15:05
discord-raku-bot joined
16:18
evalable6 left,
linkable6 left
16:19
linkable6 joined,
Altai-man left,
Altai-man joined
16:20
evalable6 joined
17:10
Altai-man left
18:06
reportable6 left
18:08
sena_kun left
18:09
reportable6 joined,
sena_kun joined
18:19
nine_ joined,
camelia left,
nine left
18:20
nine_ is now known as nine
18:24
camelia joined
19:12
sena_kun left
19:13
sena_kun joined
19:18
sena_kun left
19:19
sena_kun joined
19:24
sena_kun left
19:26
sena_kun joined
19:37
sena_kun left
19:38
sena_kun joined
19:48
sena_kun left
19:50
sena_kun joined
|
|||
| Geth | rakudo/IO.dir-with-entries: 076f484e45 | (Elizabeth Mattijsen)++ | src/core.c/IO/Path.pm6 Add an IO::Path.dir-with-entries method Checking whether a directory has entries in it, can be checked by doing e.g. an "if .dir.head {". However, this will leak resources as the iterator that runs "dir" will never be finished, and thus the underlying directory handle will also never be closed. ... (8 more lines) |
20:03 | |
| rakudo: lizmat++ created pull request #4848: Add an IO::Path.dir-with-entries method |
20:04 | ||
| SmokeMachine | Would something like this be possible? www.irccloud.com/pastebin/eFdO2yxP/ | 21:58 | |
|
22:05
ggoebel joined
22:26
ggoebel left
23:53
ggoebel joined
|
|||