Author CCLDArjun
Recipients CCLDArjun, lys.nikolaou, pablogsal
Date 2021-06-06.23:42:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623022957.88.0.314706956468.issue44324@roundup.psfhosted.org>
In-reply-to
Content
> This one will be very tricky to do correctly because the '=' is very context-sensitive and the parser can be confused when backtracking, so this *may* be quite delicate/complex

Well, I was thinking we could just do a simple check in _PyPegen_check_tokenizer_errors or _PyPegen_run_parser functions. If the last three tokens in the Parser object's tokens array are NAME, EQUAL/MINEQUAL/etc and NEWLINE, we raise the special error. Is this the right way to do it? I saw that unclosed parentheses' special error are checked in the same place. 

> I suspect this is going to be a pain for malformed expressions on the right

Yea, I realized that the "expected an expression" error can be used in multiple places. Could be added one by one?
History
Date User Action Args
2021-06-06 23:42:37CCLDArjunsetrecipients: + CCLDArjun, lys.nikolaou, pablogsal
2021-06-06 23:42:37CCLDArjunsetmessageid: <1623022957.88.0.314706956468.issue44324@roundup.psfhosted.org>
2021-06-06 23:42:37CCLDArjunlinkissue44324 messages
2021-06-06 23:42:37CCLDArjuncreate