[Async-sig] New blog post: Notes on structured concurrency, or: Go statement considered harmful

[Guido van Rossum]

Now there's a PEP I'd like to see.

On Wed, Apr 25, 2018 at 2:24 AM, Nathaniel Smith <njs at pobox.com> wrote:

> Hi all,
>
> I just posted another essay on concurrent API design:
>
> https://vorpus.org/blog/notes-on-structured-concurrency-or-
> go-statement-considered-harmful/
>
> This is the one that finally gets at the core reasons why Trio exists;
> I've been trying to figure out how to write it for at least a year
> now. I hope you like it.
>
> (Guido: this is the one you should read :-). Or if it's too much, you
> can jump to the conclusion [1], and I'm happy to come find you
> somewhere with a whiteboard, if that'd be helpful!)
>
> -n
>
> [1] https://vorpus.org/blog/notes-on-structured-concurrency-or-
> go-statement-considered-harmful/#conclusion
>
> --
> Nathaniel J. Smith -- https://vorpus.org
> _______________________________________________
> Async-sig mailing list
> Async-sig at python.org
> https://mail.python.org/mailman/listinfo/async-sig
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>



-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/async-sig/attachments/20180425/acac8cdb/attachment.html>