Parse ellipsis (...) in the old parser #503
Conversation
|
@Thirumalai-Shaktivel if you wouldn't mind adding tests for .. and None, then we can merge this. |
| @@ -83,6 +83,8 @@ module LPython | |||
| | ConstantBool(bool value, string? kind) | |||
| | ConstantFloat(float value, string? kind) | |||
| | ConstantComplex(float re, float im, string? kind) | |||
| | ConstantEllipsis(string? kind) | |||
There was a problem hiding this comment.
How are we going to support this in the ASR?
There was a problem hiding this comment.
I think ... is similar to pass, so that's just an empty subroutine, so you leave the body argument empty in ASR.
There was a problem hiding this comment.
What I've noticed is that people use Ellipsis to indicate something they want to fill in later (like a todo empty block) and pass stmt to mean a block is intended to have no code.
... is used in NumPy code, too, as a placeholder in slice notation.
See more uses here: https://python.land/python-ellipsis
There was a problem hiding this comment.
It has different uses. For the "empty block" use, we can just represent that with an empty block in ASR.
|
Thanks! |
No description provided.