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

Potentially confusing behaviour of using and hiding for import #3317

Open
janmasrovira opened this issue Feb 3, 2025 · 0 comments
Open

Potentially confusing behaviour of using and hiding for import #3317

janmasrovira opened this issue Feb 3, 2025 · 0 comments

Comments

@janmasrovira
Copy link
Collaborator

janmasrovira commented Feb 3, 2025

Example:

module example;

import Stdlib.Prelude;
import Stdlib.Prelude using {Bool};

x : Stdlib.Prelude.Bool := Stdlib.Prelude.true; -- error: Stdlib.Prelude.true is not in scope

It might be counterintuitive that the second import shadows/overwrites the first one.
I think it would be less confusing if imports behaved additively. I.e. the same way as open statements. Then, the above example should typecheck.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant