🦋 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:02
reportable6 joined
00:42
Geth left,
Geth joined
02:06
linkable6 left,
evalable6 left,
linkable6 joined
02:07
evalable6 joined
04:04
kjp left
04:07
kjp joined
05:50
shareable6 left,
bisectable6 left,
bloatable6 left,
reportable6 left,
committable6 left,
notable6 left,
unicodable6 left,
releasable6 left,
coverable6 left,
statisfiable6 left,
squashable6 left,
tellable6 left,
nativecallable6 left,
sourceable6 left,
greppable6 left,
evalable6 left,
linkable6 left,
quotable6 left,
benchable6 left
05:51
statisfiable6 joined,
reportable6 joined,
linkable6 joined,
shareable6 joined,
evalable6 joined
05:52
tellable6 joined,
bisectable6 joined,
sourceable6 joined,
coverable6 joined,
committable6 joined,
greppable6 joined
05:53
releasable6 joined,
bloatable6 joined,
quotable6 joined,
nativecallable6 joined,
squashable6 joined,
notable6 joined,
unicodable6 joined,
benchable6 joined
06:00
reportable6 left
06:01
reportable6 joined
07:00
samcv left
08:05
tellable6 left,
evalable6 left,
unicodable6 left,
sourceable6 left,
coverable6 left,
committable6 left,
releasable6 left,
notable6 left,
squashable6 left,
benchable6 left,
shareable6 left,
nativecallable6 left,
statisfiable6 left,
bloatable6 left,
reportable6 left,
quotable6 left,
bisectable6 left,
linkable6 left,
greppable6 left
08:06
quotable6 joined,
statisfiable6 joined,
committable6 joined,
releasable6 joined,
coverable6 joined,
evalable6 joined,
benchable6 joined,
squashable6 joined,
unicodable6 joined
08:07
notable6 joined,
tellable6 joined,
greppable6 joined
08:08
bisectable6 joined,
bloatable6 joined,
shareable6 joined,
sourceable6 joined,
nativecallable6 joined,
linkable6 joined,
reportable6 joined
10:01
sena_kun joined
|
|||
bartolin_ | bisectable6: role R { method m (*@a) { ... } }; class C does R { multi method m (*@a) {} } ## github.com/Raku/old-issue-tracker/issues/2901 | 10:28 | |
bisectable6 | bartolin_, Will bisect the whole range automagically because no endpoints were provided, hang tight | ||
bartolin_, Output on all releases: gist.github.com/aea0e47332378a5402...eb075bc7a0 | 10:29 | ||
bartolin_, Bisecting by exit code (old=2018.09 new=2018.10). Old exit code: 1 | |||
bartolin_, bisect log: gist.github.com/78134ec9e95cb8f6d9...35cb36f3c7 | |||
bartolin_, (2018-10-18) github.com/rakudo/rakudo/commit/fd...6eea7ca92f | |||
bartolin_, Bisecting by output (old=2016.11 new=2016.12) because on both starting points the exit code is 1 | |||
bartolin_, bisect log: gist.github.com/9def0d3c176af04771...6302ffa02e | |||
bartolin_, (2016-12-12) github.com/rakudo/rakudo/commit/7e...0edc7d1e1a | |||
bartolin_, ⚠ New output detected, please review the results manually | |||
bartolin_, Output on all releases and bisected commits: gist.github.com/6f70c2e34046dcac73...bcb45b39dd | |||
11:14
frost joined
12:00
reportable6 left
12:02
reportable6 joined
|
|||
lizmat | ab5tract: so is github.com/rakudo/rakudo/pull/5207 ready for merge? and should it be a squash merge ? | 12:15 | |
nine | I haven't submitted my review yet | 12:16 | |
lizmat | cool, I'll hold off then :-) | ||
nine | I don't really like the way the meta object handling is set up, but I haven't yet the time to think through an alternative | 12:17 | |
lizmat | ok, I'd better mark it as draft then? | ||
Geth | nqp/main: 30593cdc28 | (Elizabeth Mattijsen)++ | src/HLL/Grammar.nqp Remove superfluous opener/closers Spotted by tbrowder++ |
12:28 | |
12:32
samcv joined
|
|||
ab5tract | nine: Yeah, I wish the meta object handling could be done differently too. Looking forward to hearing any alternatives | 12:52 | |
nine | Well, creating the meta object can still happen in PRODUCE-META-OBJECT. You just need to collect the required info before (via that BEGIN handler) | 12:56 | |
ab5tract | but then how do I run apply-traits with all of the relevant roles already added? | 13:02 | |
is that safe to do at CHECK time? | |||
Also, I need the meta object to have those roles applied before I can rebless | 13:03 | ||
so unless I can move all of the declaration and installation to check time, I'm not sure how to adopt your approach | 13:05 | ||
lizmat | ab5tract: what is the meaning of $!of in the enum context ? | 13:15 | |
ab5tract | it's the RakuAST::Type node provided to specify the base type | 13:16 | |
we get it from $<OFTYPE> in Actions | |||
lizmat | right | 13:17 | |
ok, then I got the deparse lined up for just after the merge :-) | 13:18 | ||
ab5tract | I know there is a mismatch between how RakuAST::Type::Subset (now) takes a RakuAST::Trait::Of for '$!of', but I figured we could hash that out in review | ||
nine | ab5tract: the meta object would still be produced dring PERFORM-BEGIN's runtime via a call to self.meta-object | 13:19 | |
ab5tract | I was under the impression that your suggestion was to gather the required information (essentially the base-type) during PERFORM-BEGIN | 13:20 | |
ah, wait, I think I see what you are saying now | 13:21 | ||
Geth | nqp/main: 3b410d7274 | (Elizabeth Mattijsen)++ | tools/templates/MOAR_REVISION Bump MoarVM to get getlexstatic_o with fallback resolver fix |
||
rakudo/main: e4d31e8194 | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION Bump NQP for MoarVM and NQP fixes |
13:36 | ||
13:59
evalable6 left,
linkable6 left
14:00
linkable6 joined
14:01
evalable6 joined
|
|||
ab5tract | nine: that led to a drastically cleaner PRODUCE-META-OBJECT. Thanks for the suggestion | 14:48 | |
out for now | 14:50 | ||
14:51
ab5tract left
15:20
frost left
|
|||
Geth | rakudo/main: 760e21c186 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 6 files Make log and sqrt handle negative values mathematically correct (#5192) - in 6.e only - make sqrt a multi - add a new sqrt candidate handling negative values - add a new log candidate handling negative values Note that the use of "is default" in these new candidates is needed to resolve dispatch ambiguities. This is really a stopgap measure for now, hopefully we can dispatch on language version soon! |
17:27 | |
18:00
reportable6 left
18:01
reportable6 joined
|
|||
patrickb | o/ | 19:31 | |
I'm curious: Will RakuAST strategically unblock in-process precompilation? | 19:32 | ||
bartolin_ | c: 2018.09 role R { method m (*@a) { ... } }; class C does R { multi method m (*@a) {} } | 19:49 | |
committable6 | bartolin_, ¦2018.09: «4===SORRY!4=== Error while compiling /tmp/lsAql08E81Method 'm' must be implemented by C because it is required by roles: R.at /tmp/lsAql08E81:1 «exit code = 1»» | ||
bartolin_ | c: 2018.09 role R { multi method m (*@a) { ... } }; class C does R { multi method m (*@a) {} } | ||
committable6 | bartolin_, ¦2018.09: «» | ||
bartolin_ | c: 2018.09 { my role R { multi method m (*@a) { ... } }; my class C does R { multi method m (*@a) { "OHAI" } }; my C $c .= new(); say $c.m(3) } | 20:00 | |
committable6 | bartolin_, ¦2018.09: «OHAI» | ||
bartolin_ | c: 2018.09 { my role R { method m (*@a) { ... } }; my class C does R { multi method m (*@a) { "OHAI" } }; my C $c .= new(); say $c.m(3) } | ||
committable6 | bartolin_, ¦2018.09: «4===SORRY!4=== Error while compiling /tmp/kWRbcAxsUPMethod 'm' must be implemented by C because it is required by roles: R.at /tmp/kWRbcAxsUP:1 «exit code = 1»» | ||
bartolin_ | c: 2018.10 { my role R { method m (*@a) { ... } }; my class C does R { multi method m (*@a) { "OHAI" } }; my C $c .= new(); say $c.m(3) } | 20:01 | |
committable6 | bartolin_, ¦2018.10: «OHAI» | ||
Geth | roast: usev6++ created pull request #830: Test implementing non-multi method stubbed in role |
20:05 | |
bartolin_ | c: 2018.09 role R { method f {...} }; class A { method f { } }; class B does R { has A $.a handles <f> } ## github.com/Raku/old-issue-tracker/issues/5687 | 20:08 | |
committable6 | bartolin_, ¦2018.09: «4===SORRY!4=== Error while compiling /tmp/r7RcbT9aiBMethod 'f' must be implemented by B because it is required by roles: R.at /tmp/r7RcbT9aiB:1 «exit code = 1»» | ||
bartolin_ | c: 2018.10 role R { method f {...} }; class A { method f { } }; class B does R { has A $.a handles <f> } ## github.com/Raku/old-issue-tracker/issues/5687 | 20:09 | |
committable6 | bartolin_, ¦2018.10: «» | ||
nine | patrickb: newdisp helped and RakuAST may, too. What I don't know is if I'll ever bring up the courage to give that another try. I spent more than half a year on it and gave up in the end. First time I did that | 20:24 | |
patrickb | nine: maybe someone else will give it a try. We'll See. | 20:39 | |
20:43
linkable6 left
20:44
evalable6 left
20:45
evalable6 joined
20:46
linkable6 joined
23:05
sena_kun left
|