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
[enh] Issue 12567 - Modules can't be marked as deprecated #3907
Conversation
Auto-merge toggled on |
Excellent. However, won't this require a change in the lexer spec? AFAIK the very first thing in a module should either be a shebang or the module declaration, so a |
[enh] Issue 12567 - Modules can't be marked as deprecated
@9rnsr Great enhancement. BTW, do you plan to allow other attributes for module? I tell about language attributes like |
What dmd relies on is that the first letter in any source code must be an ASCII character. |
@IgorStepanov I opened documentation fix: dlang/dlang.org#642 |
Hmm ok.
|
@9rnsr I asked about UDAs for modules like
... and about function parameter attributes:
|
@IgorStepanov If you want to request new language feature, please file it in bugzilla with reasonable use cases. |
[enh] Issue 12567 - Modules can't be marked as deprecated Conflicts: src/hdrgen.c src/module.c
https://issues.dlang.org/show_bug.cgi?id=12567
Points:
Compiler checks the deprecation when the module is imported.
ModuleDeclaraion
is necessary if you want to make the module deprecated.Deprecating a module does not deprecate its members automatically.
It's useful if you want to merely rename modules.