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

[new module system] Panic when instanitating a top-level module with undefined modules #1470

Closed
yav opened this issue Nov 17, 2022 · 0 comments
Assignees
Labels
bug Something not working correctly parameterized modules Related to Cryptol's parameterized modules

Comments

@yav
Copy link
Member

yav commented Nov 17, 2022

This example produces a panic when it should just say that X and Y are not in scope.

module T = submodule X { submodule Y }

Nothing is in scope when instantiating top-level modules, so we can probably just complain straight away if we see a non-top-level name

@yav yav added bug Something not working correctly parameterized modules Related to Cryptol's parameterized modules labels Nov 17, 2022
@yav yav self-assigned this Nov 17, 2022
@yav yav closed this as completed Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something not working correctly parameterized modules Related to Cryptol's parameterized modules
Projects
None yet
Development

No branches or pull requests

1 participant