Message 374349 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	gvanrossum
Recipients	BTaskaya, Peter Ludemann, carljm, corona10, davidhalter, eric.snow, gregory.p.smith, gvanrossum, hroncok
Date	2020-07-26.22:56:43
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1595804203.48.0.397491388447.issue40360@roundup.psfhosted.org>
In-reply-to

Content
I guess the design space is wide open. Does parso have to be pure Python? If not, we could generate C code like we do for CPython's parser. Now, that doesn't work for incremental parsing, but I did an alternative implementation that uses a stack machine, also in C, that's only 2x slower than the PEG parser. Maybe that could be adapted to incremental parsing (because it's a stack machine). Error recovery is still a research project (at least for me -- I'm actually reading papers :-).

I guess the design space is wide open.

Does parso have to be pure Python? If not, we could generate C code like we do for CPython's parser. Now, that doesn't work for incremental parsing, but I did an alternative implementation that uses a stack machine, also in C, that's only 2x slower than the PEG parser. Maybe that could be adapted to incremental parsing (because it's a stack machine). Error recovery is still a research project (at least for me -- I'm actually reading papers :-).

History
Date	User	Action	Args
2020-07-26 22:56:43	gvanrossum	set	recipients: + gvanrossum, gregory.p.smith, carljm, eric.snow, davidhalter, hroncok, corona10, BTaskaya, Peter Ludemann
2020-07-26 22:56:43	gvanrossum	set	messageid: <1595804203.48.0.397491388447.issue40360@roundup.psfhosted.org>
2020-07-26 22:56:43	gvanrossum	link	issue40360 messages
2020-07-26 22:56:43	gvanrossum	create