github.com/moarvm/moarvm | IRC logs at irclog.perlgeek.de/moarvm/today
Set by moderator on 21 May 2018.
timotimo *shrug* 00:08
01:57 ilbot3 joined
moderator github.com/moarvm/moarvm | IRC logs at irclog.perlgeek.de/moarvm/today
02:27 lizmat joined 03:41 mtj_ joined
AlexDaniel` Also your terminal 04:29
05:35 shareable6 joined 05:42 nativecallable6 joined, bloatable6 joined 05:43 quotable6 joined, coverable6 joined, releasable6 joined, greppable6 joined, reportable6 joined, bisectable6 joined, notable6 joined, committable6 joined, evalable6 joined, unicodable6 joined, benchable6 joined, statisfiable6 joined, squashable6 joined, undersightable6 joined, shareable6 joined 06:22 domidumont joined 06:28 domidumont joined 07:17 robertle joined 08:06 shareable6 joined 08:11 brrt joined
brrt good * 08:11
yoleaux 21 May 2018 15:57Z <Zoffix> brrt: did you ever write down the guide for implementing new ops? I'm taking you up on your call for adding ops that could be faster than HLL code. I need a rational-reducing op
brrt i think we want something like that for divmod? or we maybe already have it
but anyway, i'm not in favor of consing up lists in the interpreter
it is not impossible to have multiple outputs in the interpreter, but there are some pieces of code that need change probably 08:12
08:20 Kaiepi joined
brrt japhb: excellent points both 08:43
09:30 TimToady joined
Zoffix So is there a guide for new ops or isn't? 11:10
New rule: people who complain other people should be doing more of something can't say "I'm not in favour of X" and then leave when other people ask how can I do more of something. 11:11
.tell brrt that didn't really answer my question. You complained we do in HLL what's better done as an op. I asked how to make an op. You reply you're not in favour of it. That makes me feel I should stick to doing things in HLL instead of ops. If some ops are better not done, then maybe it's something you should include in an op creation guide. 11:15
yoleaux Zoffix: I'll pass your message to brrt.
11:16 Zoffix left 11:28 domidumont joined 11:29 brrt joined
brrt .tell Zoffix new rule: lets not make community law to resolve minor miscommunications 11:36
yoleaux brrt: I'll pass your message to Zoffix.
brrt :-P
anyway, i'm working on JIT improvmeents 11:38
(in so far as i have time to work on MoarVM at all)
12:04 shareable6 joined 12:14 domidumont joined 12:44 zakharyas joined 12:47 domidumont joined 13:23 domidumont joined 13:51 Kaiepi joined 14:00 Kaiepi joined
brrt ... almost got the jit return address thing fixed 14:01
except for this pesky thing of rakudo CORE.setting crashing
timotimo eh, do we really need CORE.setting for anything? 14:07
brrt can't imagine what for 14:17
samcv ok i've posted the changelog draft now github.com/MoarVM/MoarVM/wiki/ChangeLog-Draft 14:55
needs a little more cleanup though
15:15 dogbert17 joined
timotimo should we leave out changes from the chaneglog that were done to things that weren't in the previous release? 15:48
like, the slice op was just added, so it may be weird to read "modify slice op's usage of negative values" way before it's mentioned at all :P
i'll just throw out the two lines i'm refering to
can be reverted anyway
and slice being added is in there twice, but that may be okay 15:49
samcv timotimo: yeah we should 15:53
go ahead and modify since i wasn't sure everything that has been changed
well things that have changed, but have *not* changed since last release
15:58 brrt joined 16:00 domidumont joined 16:24 lizmat joined 16:53 robertle joined
Geth MoarVM: ad9ead9a43 | (Samantha McVey)++ | tools/update-changelog.p6
Some minor fixes to update-changelog.p6
16:55
MoarVM: 9b9aa8c586 | (Samantha McVey)++ | docs/ChangeLog
Update ChangeLog
18:39 shareable6 joined 19:25 AlexDaniel joined 19:27 brrt joined
samcv .tell brrt want to look over docs/ChangeLog and see if any changes need to be made before release? 20:54
yoleaux samcv: I'll pass your message to brrt.
samcv jnthn and whoever else too :) 20:55
22:33 Kaiepi joined