Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roots that are not Modules #1554

Open
Tracked by #1433
zrho opened this issue Oct 4, 2024 · 1 comment
Open
Tracked by #1433

Roots that are not Modules #1554

zrho opened this issue Oct 4, 2024 · 1 comment
Assignees

Comments

@zrho
Copy link
Contributor

zrho commented Oct 4, 2024

@aborgna-q pointed out to me that there are Hugrs whose roots are not Modules. That is currently not accounted for in the model. How do we want to deal with this? There's an argument that the root should always be a module: say it was a dataflow graph instead. The dfg then may refer to a custom type in its signature. But then we'd want a place where we can declare this custom type. If declarations are scoped in the natural way, the declaration can not be inside of the dfg, but if the dfg is the root it also can't be outside.

@aborgna-q
Copy link
Collaborator

See #1642 for a proposal solution, making all hugrs define a module.

@aborgna-q aborgna-q self-assigned this Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants