[pypy-dev] mix-and-match approach to implementation decisions

[William ML Leslie]

On 14 February 2015 at 19:48, anatoly techtonik <techtonik at gmail.com> wrote:

> Hi,
>
> Reading http://rpython.readthedocs.org/en/latest/ to see if I can
> understand the text without a formal CS education. What does
> "mix-and-match approach to implementation decisions" mean?
>

It means that making one decision - like which GC to use - does not have a
great impact on other decisions, like whether you can have a JIT.

Pypy itself is a great representation of this philosophy, where there are a
large number of 'strategies' that optimise built-in objects for different
use cases, which are enabled or disabled at translation time.

-- 
William Leslie

Notice:
Likely much of this email is, by the nature of copyright, covered under
copyright law.  You absolutely MAY reproduce any part of it in accordance
with the copyright law of the nation you are reading this in.  Any attempt
to DENY YOU THOSE RIGHTS would be illegal without prior contractual
agreement.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20150214/b7b6bf46/attachment.html>