Re: Concurrency, again

[Eli Zaretskii]

> Date: Wed, 12 Oct 2016 17:33:14 -0400
> From: "Perry E. Metzger" <address@hidden>
> Cc: Eli Zaretskii <address@hidden>, Stefan Monnier <address@hidden>,
>  address@hidden
> 
> > The thing is all current code expects to be able to access any
> > buffer they like without interferrence from other code.
> > So to make this new model work we would need to support both
> > paradigms. If any "old-style" code started execution, by being
> > called by a function or from a timer, then the entire world would
> > have to halt so the old-style code could execute with its
> > assumption of sequential access.
> 
> Well, the code expects to *access* buffers, but it doesn't expect to
> interact with other executing code.

That's not accurate, since all kinds of hooks triggered by buffer
access could execute code that accesses other buffers and changes
their contents.

> Concurrency is a giant tarpit of subtleties. :(

And Emacs is another giant tarpit.