🦋 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:08 reportable6 left 00:09 reportable6 joined 01:50 frost joined 02:27 frost left 02:30 frost joined 04:02 sourceable6 left, releasable6 left, bisectable6 left, greppable6 left, reportable6 left, benchable6 left, notable6 left, bloatable6 left, coverable6 left, unicodable6 left, tellable6 left, quotable6 left, committable6 left, linkable6 left, nativecallable6 left, evalable6 left, shareable6 left, statisfiable6 left, shareable6 joined, coverable6 joined, bisectable6 joined, tellable6 joined, committable6 joined 04:03 sourceable6 joined, bloatable6 joined, evalable6 joined, unicodable6 joined, statisfiable6 joined 04:04 greppable6 joined, benchable6 joined, linkable6 joined, quotable6 joined, releasable6 joined, nativecallable6 joined 04:05 reportable6 joined, notable6 joined 06:03 evalable6 left, linkable6 left, linkable6 joined 06:04 evalable6 joined 06:08 reportable6 left 06:10 reportable6 joined 07:10 evalable6 left, linkable6 left, linkable6 joined 07:11 evalable6 joined 07:36 [Coke]_ joined 07:37 [Coke] left
Geth rakudo/lizmat-fail-io-socket-inet: 14baac4659 | (Elizabeth Mattijsen)++ | src/core.c/IO/Socket/INET.pm6
Make unsuccessful connect fail rather than die

Spotted in stackoverflow.com/questions/726398...socketinet
There is no documentation or tests covering the behaviour of a failed connect. It is actually the nqp::connect that throws (which turns out also to be not documented BTW).
Having it return a Failure feels more natural indeed.
rakudo: lizmat++ created pull request #4957:
Make unsuccessful connect fail rather than die
09:39 committable6 left, nativecallable6 left, quotable6 left, shareable6 left, greppable6 left, coverable6 left, unicodable6 left, evalable6 left, sourceable6 left, reportable6 left, statisfiable6 left, tellable6 left, notable6 left, bloatable6 left, benchable6 left, linkable6 left, bisectable6 left, releasable6 left, coverable6 joined, nativecallable6 joined 09:40 reportable6 joined, committable6 joined, tellable6 joined, notable6 joined, shareable6 joined, greppable6 joined, statisfiable6 joined, evalable6 joined, benchable6 joined 09:41 releasable6 joined, quotable6 joined, linkable6 joined, bisectable6 joined 09:42 bloatable6 joined, sourceable6 joined, unicodable6 joined 10:42 linkable6 left, evalable6 left 10:43 evalable6 joined 10:44 linkable6 joined 11:44 linkable6 left, evalable6 left, notable6 left 11:45 notable6 joined, evalable6 joined, linkable6 joined
patrickb o/ 11:52
12:06 reportable6 left, [Coke]_ is now known as [Coke] 12:08 reportable6 joined
Geth rakudo/rakuast: 24 commits pushed by (Stefan Seifert)++
review: github.com/rakudo/rakudo/compare/c...52d61ec594
13:17 carlmasak joined
carlmasak greetings, #raku-dev 13:17
lizmat carlmasak o/ 13:20
carlmasak hi, lizmat. it must be mid-afternoon in your part of the world 13:22
lizmat yea, 15:23 or so
carlmasak here in .cn, we start every day a few hours earlier than Europe
must be the work ethic
lizmat I guess... :-) 13:23
13:23 Kaiepi joined
carlmasak :P 13:23
I know I mentioned it before, but I was one of the sad saps who bought a Beat watch from Swatch, many years ago 13:24
a "beat" is one thousandth of a 24-hour day, and you write the time like this: @499
and it's time zone independent
needless to say, this PR stunt from Swatch didn't catch on like wildfire 13:25
m: say (60 #`[seconds/minute] * 60 #`[minutes/hour] * 24 #`[hours/day]) / 1000 #`[beats/day] 13:30
camelia 86.4
carlmasak ...which makes a beat one minute and 26.4 seconds long.
lizmat feels a bit like Tau::Station::DateTime? 13:37
[Coke] does anything in the ecosystem given an idea of # of downloads/users, etc.? 13:39
lizmat raku.land keeps some stats I think 13:40
patrickb is working on the RCB (Rakudo CI Bot). 13:47
Currently implementing the branch matching logic. So when a commit in a PR should be tested it'll search for a matching branch in the respective other repos. 13:48
Should a requirement for a branch to be picked be, that a repective PR exists?
Or should it just take any same named branch in either the same project/user that the PR was created (or the rakudo/rakudo, Raku/nqp, MoarVM/MoarVM repos)? 13:50
For now I'll go with just taking any matching branch name and not requiring a PR. Please comment if you object. 13:55
nine I think that's a sensible thing to do 13:56
[Coke] I think if we were all in on an automated workflow, a PR would be required, but this matching branch-if-exists seems reasonable to me 13:57
14:24 frost left 14:38 vrurg_ is now known as vrurg 15:24 Altai-man left 15:25 sena_kun joined 16:08 carlmasak left 16:28 sena_kun left 16:30 sena_kun joined 16:55 Kaiepi left 17:24 Kaiepi joined 17:38 kawaii left 18:07 reportable6 left 18:09 reportable6 joined 19:09 evalable6 left, linkable6 left 19:10 evalable6 joined 19:11 linkable6 joined 19:20 MasterDuke left 19:34 MasterDuke joined 20:38 moon-child left 21:58 evalable6 left, linkable6 left 22:00 evalable6 joined 22:01 linkable6 joined
Geth rakudo: vlmarek++ created pull request #4959:
Todo failing test on Solaris
roast: vlmarek++ created pull request #810:
Make spectest pass on Solaris
23:07 evalable6 left, linkable6 left 23:10 evalable6 joined, linkable6 joined