12f99a9cc7
nac3core: test snap files
b9bed52340
nac3core: clean up and fix for test
236dfb438b
nac3artiq: change device to riscv
6eca0712b0
nac3standalone, nac3artiq: update demo
d573ed81f7
nac3core, nac3artiq: typevar only in function method
447fc5b6b0
for debug only
87a80fbd76
added kernel print to terinal
14d29237d8
symbol resolver basic typevar handling
4b1663324d
nac3core: type annotation better error message
032e1d84cf
nac3parser: add and fix tests due to comment support
b239806558
nac3core: adapt to ast change due to comment support
694c7e945c
nac3ast: generated ast with comment fields
3b1cc02d06
nac3parser, ast: add comment support core changes
39c5d171a7
nac3parser: add comment support
nac3parser: add comment support
39c5d171a7
nac3parser: add comment support
32d1fe811b
flake: update nixpkgs
36e4028f5b
fix and run parser tests
b6ff46c39e
README: update
bf7e2c295a
integrate nac3parser
830652a276
symbol resolver basic typevar handling
b72385938b
nac3core: type annotation better error message
08ab923e21
update parser mod, fix location, allow semicolon before the tail comment
9fb39da930
update parser mod, fix location, allow semicolon before the tail comment
add comment support to rustpython parser
But why can't we associate the first comment to the if statement and the second comment to the
b = 1
statement?
Thanks for the suggestion, I have added this support in the [latest…
add comment support to rustpython parser
what do you mean by
this should attach to
if
can the whole program should not parse?
sorry, please just ignore the content of the previous comment. Let me explain again:
I mean…
add comment support to rustpython parser
The updated with_nac3comment branch contains updates related to previous discussion, including:
- avoid NAC3 references in the…
cd9801516a
nac3core: use updated moded parser
798da2d444
nac3core: use updated moded parser
798da2d444
nac3core: use updated moded parser
ede2ea7b1c
use parser with nac3 comment support
fd0b11087e
nac3core: use round instead of rint. Closes #61
3a1dd893a1
nac3artiq/demo: get closer to regular ARTIQ
a4ccac2329
nac3artiq: implements #55, #56
poor error message with incorrect method return type
now the error msg looks like:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "expected return type of `int32` in function `__main__A.get_a` at line 13 column 5"',…
4fcb54e463
nac3core: fix #46, better toplevel return type error msg
52b5222201
nac3core: fix #46, better toplevel return type error msg