module type support #40

New Issue

sb10q · 2021-10-02T19:09:07+08:00

sb10q commented

2021-10-02 19:09:07 +08:00

Currently the type system is not able to represent Python modules, so names cannot be modules and therefore statements like import xxx do not work (as the module xxx cannot be bound to the namespace).

The bare minimum required to support import xxx and import xxx as yyy would be sufficient, i.e. we do not have to support modules passed as function parameters, returned from functions, assigned to variables, etc. etc.

See also #36 (comment)

Currently the type system is not able to represent Python modules, so names cannot be modules and therefore statements like ``import xxx`` do not work (as the module ``xxx`` cannot be bound to the namespace). The bare minimum required to support ``import xxx`` and ``import xxx as yyy`` would be sufficient, i.e. we do not have to support modules passed as function parameters, returned from functions, assigned to variables, etc. etc. See also https://git.m-labs.hk/M-Labs/nac3/issues/36#issuecomment-2668

sb10q added the

low-priority

label 2021-10-02 19:09:07 +08:00

sb10q referenced this issue

2021-10-02 19:09:22 +08:00

multi module support in nac3artiq #36

pca006132 referenced this issue

2021-11-06 19:05:48 +08:00

define parallel/sequential in nac3artiq Rust side #74

pca006132 referenced this issue

2021-11-06 23:22:18 +08:00

Make constructs rename/module aware? #78