Is this done?
Not yet. There seems to be not much progress on this on how Python will resolve this.
A proper fix would be to change the type system to allow for iterator type, which can be range type, list type or other user defined iterators.
Ah I get it, yes and I think for this issue (#137)…
I meant
Default
forComposerConfig
.
Implemented in the new commmit.
Misleading comment. I suggest removing it, since it's fairly obvious what this does from the code already.
Oh I see, removed in the latest commit.
We may want to refactor this at some point…
I think for some more time and the major problem seems to be the unification between the type var var1(range = [list[var2], range])
(list of something or range), and the type `list[some concrete…
I think this field initialization check problem is also related to the super
(#136) and somehow related to the module type (#40) (should be 'class type' here though).. So maybe we should settle how…
Things related to the slice also needs these array bounds checks.. I am not sure.. should this be implemented after the exception since array bound cannot be easily checked statically?
Thanks for the above suggestions, they are implemented in the new commits.
Currently we are always in
__init__
since there is no RPC.
Sorry I think I do not quite get what you mean here, now in nac3artiq we are also outside of __init__
when we are not constructing…
Thanks a lot for the information! I implemented again using this now.