We should ban reading from submodule inputs #77
Comments
|
Also, this shrinks the complexity of the language a little, which is a nice bonus ^-^ |
|
Thinking further, I'm starting to think unconditional ports should only be accessed either on the module instantiation itself (via func call syntax), or on module domains. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The main triggering reason is that Latency Inference can't deal with inputs that are again read. Because then the latency offset between two ports may shrink because of another relaxation, and that would lead to incorrect inferences.
Going even further, perhaps we can bake this inability into the language structure itself, by only allowing port access through the function-call syntax
The text was updated successfully, but these errors were encountered: