-
Notifications
You must be signed in to change notification settings - Fork 317
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
Export FQN without any imports #9562
Comments
Pavel Marek reports a new STANDUP for today (2024-04-11): Progress: - Tweaked the import/export resolver to insert synthetic imports in certain cases.
|
The #9683 PR fixes all but "Support import ... followed by simple non-qualified export Platform" (low priority) task, right? |
@JaroslavTulach No. The following snippet:
Results in a compilation error:
Theoretically, it should work. But since we already support only exports without imports, I don't see any added value to this functionality. |
The import/export documentation has been incorrectly understood leading to an obscure, verbose, do repeat yourself usages polluting all our standard libraries.
For a while I am puzzled, by our usual code that imports and exports at once:
as shown for example in here. It is not really DRY, right?
Reading the Qualified Exports section, I believe the specification actually says that we should be able to do just:
There's no point to import FQN and export FQN. Let's not spell FQN twice! Alternatively one could write:
that'd also logical and rationalistic. But the current use of doubled FQN in export and import is just unnecessary boilerplate.
Tasks
The text was updated successfully, but these errors were encountered: