News for hackers. Stuff that matters.
Re:I don't understand Python's Asyncio by mzs on Sunday October 30, 2016 @02:16PM (#12831299)
http://libmill.org/documentation.html

  Libmill runs in following environments:

  Microarchitecture: x86_64, ARM
  Compiler: gcc, clang
  Operating system: Linux, OSX, FreeBSD, OpenBSD, NetBSD, DragonFlyBSD

  Whether it works in different environments is not known - please, do report any successes or failures to the project mailing list.
Re:I don't understand Python's Asyncio by danappelxx on Sunday October 30, 2016 @10:24PM (#12833888)
He was not suggesting to adopt libmill, only to adopt a similar concurrency scheme.
Re:I don't understand Python's Asyncio by mzs on Wednesday November 02, 2016 @01:00PM (#12856900)
I wasn't saying that either, I was saying libmill did not do it in (pure) C:

https://github.com/sustrik/libmill/blob/master/libmill.h

It only works with gcc and clang now, no longer with windows, and is sprinkled with asm()s. That doesn't fly with the CPython is portable. I don't know how these go-like features could be created with ANSI C, but I'd love to be proven wrong.