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

William ML Leslie william.leslie.ttg at gmail.com
Sat Feb 14 12:11:28 CET 2015


​I guess it's reasonable to ask how true this is of rpython.  What options
are there, and how do they exclude / depend on one another?  In the l*o*p
problem, it now ignores all p but one, and rpython doesn't concern itself
with l.​  Maybe it's the gc * o problem now?

-- 
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/de3bb0a5/attachment.html>


More information about the pypy-dev mailing list