Mark @pysoniq wrote:

It would be most helpful if you could provide an example of how they contain
"few technical details."  I ask because I was afraid they were too technical!

Your blog posts about optimisation mostly talk about standard
things that have been known for decades. E.g. "keep variables
in registers" -- yes, of course, any compiler worth its salt
will try to do that.

Also, it's all very low-level stuff that applies equally to
any language. You've said nothing about how you approach the
unique challenges of compiling Python, which stem from the
fact that you're trying to bridge the gap between a very
high-level programming model and a very low-level one.

How do you deduce when the program is dealing with things like
ints and floats that are amenable your low-level optimisations?
Have you come up with some clever techniques that do a better
job of this than other attempts, such as Nuitka?

These are the kinds of details that would actually make people
take an interest in your project.

--
Greg
_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-le...@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at 
https://mail.python.org/archives/list/python-ideas@python.org/message/2PB24PBR3VCSSGJGKGPQKYCSN7GED7CQ/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to