Also panic in nac3standalone is acceptable, this is just a demonstration program.
Ok I see, I will remove the commits about removing panics.
Hi, the new commits resolves the conflict, and support iteration over multiple typevar assignments in the same line. I will also see if my previous PRs introduce the bug newly found..
Thanks for pointing this out, yes this and the previous issue about iterating over assignment should be resolved. Sorry that I forgot to handle these earlier..
Since this is basically the same…
This is supported in the latest commit, as well as a better type check for default parameter, please have a review, thanks!
To change the way to check whether a function is instantiated (e.g., as long as there exits one uninstantiated type vars, the function is not instantiated)
Thanks for pointing it out, I will also…
Yes, here since we are concretizing types, all class fields should not have type vars. But due to partial instantiation of class methods, there might still be some methods whose signature contains…
Sorry for the unclear comment. Here I mean that before this line in min_artiq.py: compiler = nac3artiq.NAC3(core_arguments["target"]), the class virtual should already be known to CPython…
Oh sure, now the symbol resolver change is ok, I will add this support now.
Would it be acceptable that in artiq, we just enforce and document that the self should always be self and should not be named arbitrarily? As I think this would not cause very big problems and…
I have added the basic module primitive/tuple global default parameter in the new commit.
No eval is used, only simple variable name is supported, but still involve some changes in symbol…