spino17 / jarvil Goto Github PK

if you have a jarvil code like this:

def main():
    // some code here
   # This is a comment<ENDMARKER>

where <ENDMARKER> is just for illustrating that it's the end of file here.
Problem:
# This is a comment does not appear in the generated pycode.
So any trivia that relates into <ENDMARKER> if <ENDMARKER> is occuring on an independent line does not show up in generated pycode.

Currently, one is able to do basic cargo build. In order to get started, it's a good idea to have a very simple jarvil program that can be tried using one of the cargo commands.

This can be documented in README.rst and then later more examples can be added.

There are few things which Jarvil does originally and diverge from Python. One such thing is block comments. Currently Jarvil parser does not throw error for unindented block comments however in the generated pycode that becomes a syntax error which is then thrown by Python.

Exponent operators should be included in the language

Even though Jarvil is still a small language, we need extensive test suite that covers major modules like lexer, parser, resolver and typechecker.