Experiments with thread pools: https://github.com/Araq/malebolgia
Contributions/feedback welcome.
Why now? Because it's a great new pun and I want to take credit for it.
Why now? Because it's a great new pun and I want to take credit for it.
Ahh, good old naming-driven development. I'm a fan myself :-)
Ahh, good old naming-driven development
Nice, I've never heard this term before.
Looks similar to https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/ - which is quite promising. I wonder if something similar could be used with async workers to solve the problem of unhandled exceptions.
BTW is the name meant to refer to https://en.wikipedia.org/wiki/Malebolgia or https://en.wikipedia.org/wiki/Malebolge ?
Looks similar to https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/ - which is quite promising.
That was one source of inspiration, yes.
BTW is the name meant to refer to https://en.wikipedia.org/wiki/Malebolgia or https://en.wikipedia.org/wiki/Malebolge ?
Can someone look at this Malobolgia issue: https://github.com/Araq/malebolgia/issues/37
Thanks
I'm using this in a procedure:
proc sound_alarm() =
const filename = "mixkit-uplifting-flute-notification-2317.wav"
malebolgia_master.spawn soundutils.play_wav(filename) -> malebolgia_result
Both malebolgia_master and malebolgia_result are globals. But the spawn always blocks until the sound is played to the end. Is there a way to spawn-and-forget?