github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
japhb timotimo: I'd love to see if the ratios between those different timings in your faster FASTA post remain the same in the post release optimizations branch (and if not, how much the landscape changes). 02:12
timotimo TBH i was running the post-release optimizations branch the whole time 02:13
japhb *chuckle* OK, that's not the answer I expected, but it's a good one. :-) 02:14
timotimo which also means it won't get better by applying post-release-opts a second time :(
japhb True
samcv AlexDaniel: getting the release going at this moment 16:52
AlexDaniel that's nice 16:54
nine Oh...just stumbled over a bug in handling rw ints in JIT compiled calls to JIT compiled native subs 17:09
Geth MoarVM: 2a5027ce2c | (Samantha McVey)++ | docs/ChangeLog
Update ChangeLog for release
18:49
travis-ci MoarVM build failed. Samantha McVey 'Update ChangeLog for release' 19:08
travis-ci.org/MoarVM/MoarVM/builds/423436302 github.com/MoarVM/MoarVM/compare/6...5027ce2cc6
Geth MoarVM/refs/tags/2018.08: f60b3515a8 | (Samantha McVey)++ | VERSION
Bump VERSION to 2018.08 for release
20:00
MoarVM: f60b3515a8 | (Samantha McVey)++ | VERSION
Bump VERSION to 2018.08 for release
20:01
Kaiepi something's that been bugging me a while about my pullreq for getting socket fds from async sockets for a while 21:40
it'd be useful to be able to get the server's socket's fd before having to wait for a client to connect 21:41
is there some way to accomplish that that i'm not realizing?
it'd be useful to know what the server's socket is as soon as it's instantiated, since using setsockopt on it transfers the same options to client sockets in certain cases 21:42
rather than having to wait until a client connects before you can do anything with it