Fix #324: Keep track of instance-only imports#380
Merged
jespercockx merged 4 commits intoagda:masterfrom Dec 17, 2024
Merged
Conversation
… modules with current module as prefix
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes #324 by keeping track of instances that should be imported from other modules, and generating an empty import list if necessary.
One minor aesthetic problem is that if you have a qualified imports and you also use instances from that module, there will be two imports: one qualified one and one instance-only (unqualified) one. This could probably be fixed too by a smarter way of merging imports, but it doesn't affect correctness so I'm leaving it as-is for now.