Next steps in PyPy investigations

[Bryan O'Sullivan]

On Thu, Feb 11, 2016 at 1:36 PM, Sean Farley <sean at farley.io> wrote:

> This is all really, really awesome. Yuya demoed an example of this at
> the London sprint but warned that the forking model would need to be
> different. Do you think that will be hard to accomplish this go-round?
>

Hard to say, since I haven't really looked at the chg code myself.

On the simplest level, tweaking chg to use threads instead of forking is
just a one-liner. Beyond that, there'll be presumably a lot of details to
work out around getting threading to actually work right, mostly around
accidental use of what will under this model become shared mutable state.
These are problems that I think TortoiseHG doesn't run into because its UI
can enforce a single operation at a time, whereas hg hidden behind chg has
to remain responsive and work correctly if you're running two operations
concurrently in different terminals.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20160211/048fc7bd/attachment.html>