News for hackers. Stuff that matters.

A comment on Libdill: Structured Concurrency for C (2016). Parent comment

Re:Libdill: Structured Concurrency for C (2016) by Peaker on Sunday December 24, 2017 @11:53AM (#16000225)
Then avoid blocking system calls.

When you can't, defer them to a thread that can be ignored.

[ Parent | on HN ]
Re:Libdill: Structured Concurrency for C (2016) by aidenn0 on Wednesday December 27, 2017 @04:12PM (#16018080)
That's a huge footgun in an environment where blocking calls are the default way to get almost anything done, and some calls cannot be made non-blocking.
[ Parent | on HN ]
Re:Libdill: Structured Concurrency for C (2016) by Peaker on Wednesday December 27, 2017 @05:17PM (#16018528)
True, but we don't have much trouble with it though. We don't directly call syscalls but use our own wrappers that take care of this for us.
[ Parent | on HN ]
Re:Libdill: Structured Concurrency for C (2016) by aidenn0 on Wednesday January 03, 2018 @08:16PM (#16067139)
Sorry for the late reply, but I just saw this reply. Can you share who "we" are? I'm always interested in new practical systems for concurrency.
[ Parent | on HN ]