github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
brrt \o 06:28
nwc10 o/ 06:30
brrt (and something more complex than add_i would have significantly more nodes, and as such have a much later overhead from a double-linked-list structure)
but the real reason is that I've started liking working with arrays much more in C, than with 'objects' 06:31
brrt www.microsoft.com/en-us/research/w...017mem.pdf this is fascinating stuff, I think 06:43
they claim to have a 'safe' implementation of free() 06:44
and I believe them
timotimo from just reading a little bit, it seems like it's kind-of-sort-of stochastically ensuring proper exceptions be thrown when deletes aren't correct, and also requires knowledge of what is or isn't pointers on the heap, much like a GC would do 09:59
i wonder how much faster it'd be to have a "shadow map" of memory that has 1s where the "real" memory has gc-managed pointers 10:00
brrt it's funny (and somewhat annoying) how they refer to a 'strongly typed language' 13:48
as if strongly typed is well-defined
I expect better from microsoft research
(what they mean, in this case, is a dynamically typed language, in that the runtime maintains the type of the values)
dogbert17 jnthn: you around? 18:04
have a question regarding the Proc:Async example here: docs.perl6.org/type/Proc::Async 18:05
is the handling of processes which take too long correct, i.e. what will happen after the 'Promise in(5)' block calls '$proc.kill'. Will the block in 'whenever signal(SIGTERM).merge: signal(SIGINT)' ever be called? 18:07
timotimo the process that's doing the .kill will not receive a signal
dogbert17 timotimo: who will receive it then?
if any
timotimo the process you've spawned receives what you do with proc.kill 18:08
the whenever signal(...) will receive signals you send to the perl6 process, for example by pressing ctrl-c or killing it from a process manager
i'm not sure it's possible to "receive signals for another process" easily
dogbert17 aha 18:09
so the when '$proc.kill' is called, from the 'Promise in(5)' block we'll jump directly to the 'whenever $proc.start' block? 18:10
timotimo indirectly, but yes 18:16
i mean, the process can ignore SIGHUP or react to it by doing stuff other than terminate 18:18
SIGKILL on the other hand doesn't give the process a chance to react at all
dogbert17 timotimo++ I believe I get it (famous last words) 18:20
timotimo your insight could surely be translated into a helpful piece of prose in the docs? :)
dogbert17 :) 18:21

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!