Skip to content
New issue

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

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

Already on GitHub? # to your account

Feature request: test that no two modules export the same name #291

Open
Octogonapus opened this issue May 1, 2024 · 0 comments
Open

Feature request: test that no two modules export the same name #291

Octogonapus opened this issue May 1, 2024 · 0 comments
Labels

Comments

@Octogonapus
Copy link

This is a feature request for a check that each module's set of exported names is totally unique. I'm talking about this scenario:

julia> module A
       export foo
       foo()=1
       end
Main.A

julia> module ^C

julia> module B
       export foo
       foo()=1
       end
Main.B

julia> using .A

julia> using .B

julia> foo
WARNING: both B and A export "foo"; uses of it in module Main must be qualified

You can see that both modules export the same name, and therefore its use must be qualified. I'm developing a set of packages containing autogenerated bindings, and sometimes we end up with two packages generating overlapping bindings. This is our fault, but it can be hard to check. If Aqua had a check like this, that would be very helpful.

I can put some time into developing this if this feature would be accepted. I'm also 100% okay with this being behind some feature flag, because I would expect that most users don't want such a check.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants