Perl 6 - the future is here, just unevenly distributed

IRC log for #moarvm, 2016-03-18

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:38 Unavowed joined #moarvm
01:00 lizmat joined #moarvm
03:05 mojca joined #moarvm
03:09 FROGGS joined #moarvm
03:21 colomon joined #moarvm
04:37 vendethiel joined #moarvm
05:04 leedo joined #moarvm
07:00 domidumont joined #moarvm
07:04 domidumont joined #moarvm
07:07 mojca joined #moarvm
07:14 domidumont joined #moarvm
07:47 FROGGS joined #moarvm
07:52 domidumont joined #moarvm
07:58 dalek MoarVM/heap-profiler: 09a807b | timotimo++ | src/profiler/heapsnapshot.c:
07:58 dalek MoarVM/heap-profiler: make strings in heap snapshot easier to parse
07:58 dalek MoarVM/heap-profiler:
07:58 dalek MoarVM/heap-profiler: by dropping the trailing semicolon
07:58 dalek MoarVM/heap-profiler: review: https://github.com/MoarVM/MoarVM/commit/09a807baa5
07:58 timotimo having to put a "next unless" in my parser annoyed me, so i decided to drop the trailing semicolon long before output
08:05 timotimo strange. i see a bunch of collectables here that have a non-zero index into the references list, but claim they have 0 references
08:06 timotimo that's either a bug, where we're losing references, or it's an opportunity to save a few bytes in the output by dropping the index, too
08:19 timotimo i created a new API function for adding a permanent root with a description and changed all occurences in moarvm
08:21 dalek MoarVM/heap-profiler: 2e60416 | timotimo++ | src/ (12 files):
08:21 dalek MoarVM/heap-profiler: root_add_permanent was API, so _desc gets a new function.
08:21 dalek MoarVM/heap-profiler:
08:21 dalek MoarVM/heap-profiler: without description, it'll just put a <??> into the description field
08:21 dalek MoarVM/heap-profiler: review: https://github.com/MoarVM/MoarVM/commit/2e60416d24
08:21 dalek MoarVM/heap-profiler: 9d871d4 | timotimo++ | src/profiler/heapsnapshot.c:
08:21 dalek MoarVM/heap-profiler: we always set the refs_start, even if num_refs is 0
08:21 dalek MoarVM/heap-profiler:
08:21 dalek MoarVM/heap-profiler: so we can drop a few bytes of output by resetting it to 0
08:21 dalek MoarVM/heap-profiler: if there are no refs at all.
08:21 dalek MoarVM/heap-profiler: review: https://github.com/MoarVM/MoarVM/commit/9d871d4437
08:21 timotimo there's those things
08:24 mojca joined #moarvm
08:41 zakharyas joined #moarvm
09:26 jnthn timotimo: The index is where the references would be
09:26 jnthn 0 is a valid index too so it's no less confusing that way... :)
09:26 jnthn Smaller though :)
10:18 lizmat joined #moarvm
10:24 TimToady joined #moarvm
10:35 vendethiel joined #moarvm
11:32 vendethiel joined #moarvm
14:07 timotimo jnthn: feel very free to dump (haha) my commit that dumps the heap data and push your own dump code over it
14:21 colomon_ joined #moarvm
14:29 mojca joined #moarvm
14:51 mojca joined #moarvm
16:16 * jnthn figures he'll spend that last bit of the working week on the profiler :)
16:16 jnthn Well, heap dumper
16:25 timotimo wow, holy crap, did you see this. Feathers 2.0 is a real-time javascript framework
16:25 timotimo i really didn't expect this would be possible at all
16:29 timotimo or could it be they are just saying "real-time" and not understanding what that means, like, at all?
16:31 jnthn "real time web"?
16:31 jnthn Which is nothing to do with real time
16:33 timotimo "A minimalist real-time framework for tomorrow’s apps"
16:33 timotimo is "real time web" something that actually means something?
16:33 jnthn Well, I think mojo calls itself a real time web framework...
16:34 jnthn It'd be better named pushy web
16:34 timotimo comety web :)
16:34 jnthn As it seems to largely revolve around applications to push stuff out to the browser :)
16:34 timotimo comet me, bro
16:34 jnthn :D
16:34 jnthn The terminology was probably coined in JavaScript land though :P
16:35 timotimo OK, i wouldn't expect javascript engineers to be acutely aware of what "real-time" means
16:35 jnthn aye :)
16:35 timotimo it's out of reach to them. and also not useful to them at all
16:35 timotimo when will perl6 allow for real-time stuff? :)
16:35 jnthn Technically I suspect you could do hard real-time programming in JavaScript. But...probably not on v8 :)
16:35 timotimo actually, i haven't a clue what that actually entails
16:35 jnthn Since you'd likely depend on a real time GC for starters
16:35 timotimo yeah, that's one of the hard parts
16:36 jnthn I only ever worked at one place doing hard realtime stuff
16:36 timotimo though, of course real-time GC is easy to do if you're allowed to use infinitely much ram :D
16:36 jnthn (Of the "if we miss the deadlines people can die" kind)
16:36 timotimo aye
16:38 timotimo i shouldn't allow myself to get so worked up over terminology
16:39 jnthn :)
16:39 timotimo just like when i see someone show off their latest "speed painting" ... and then it turns out it's a timelapse of slow/regular-speed painting
16:41 * jnthn grins at the union with members ric and erized
16:41 timotimo unionric and unionerized? huh?
16:42 jnthn st->paramet.erized.parametric_type, st->paramet.ric.lookup, etc. :)
16:43 timotimo oooh
16:50 dalek MoarVM/heap-profiler: fd54ad0 | jnthn++ | src/profiler/heapsnapshot.c:
16:50 dalek MoarVM/heap-profiler: Include all STable data into heap snapshot.
16:50 dalek MoarVM/heap-profiler: review: https://github.com/MoarVM/MoarVM/commit/fd54ad05d9
16:54 dalek MoarVM/heap-profiler: 15569ad | jnthn++ | src/profiler/heapsnapshot.c:
16:54 dalek MoarVM/heap-profiler: Add missing snapshot collection cleanup.
16:54 dalek MoarVM/heap-profiler: review: https://github.com/MoarVM/MoarVM/commit/15569addf3
16:55 jnthn I think that just leaves call frames, in order to actually cover all the data on the heap
17:08 FROGGS joined #moarvm
17:17 mojca joined #moarvm
17:25 dalek MoarVM/heap-profiler: 5ead72d | jnthn++ | src/profiler/heapsnapshot. (2 files):
17:25 dalek MoarVM/heap-profiler: Build up static frames info table.
17:25 dalek MoarVM/heap-profiler:
17:25 dalek MoarVM/heap-profiler: So we'll be able to understand where call frames in the heap come
17:25 dalek MoarVM/heap-profiler: from.
17:25 dalek MoarVM/heap-profiler: review: https://github.com/MoarVM/MoarVM/commit/5ead72d712
17:25 jnthn Enough for now :)
17:38 timotimo i already wondered if we want to output a stack trace for each of the heap snapshots, too
17:38 timotimo but i suppose that's more or less what we'll get now
17:38 timotimo jnthn: could you also push your dumping code into a branch or something? so that i don't duplicate your work (in an inferior manner, probably) again? ;)
17:40 mojca joined #moarvm
17:41 timotimo jnthn: do you want me to go ahead and build some kind of output stuff for the static frames? i don't see them get output'd anywhere yet
18:01 domidumont joined #moarvm
18:15 colomon joined #moarvm
18:51 mojca joined #moarvm
19:27 mojca joined #moarvm
19:52 cognominal joined #moarvm
20:47 zakharyas joined #moarvm
20:59 vendethiel joined #moarvm
21:16 zakharyas joined #moarvm
21:22 pochi joined #moarvm
21:25 btyler joined #moarvm
21:25 mst joined #moarvm
21:26 diakopter joined #moarvm
22:52 colomon joined #moarvm

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary