Proposal: #ModuleAnnotations and #ModuleDeprecation

[mark.reinhold at oracle.com]

2016/6/29 2:08:38 -0700, Remi Forax <forax at univ-mlv.fr>:
> ...
> 
> I like both proposals, adding annotations and imports on module.
> 
> I disagree that those annotations should not be visible at runtime, i
> don't see why we need a special case here, it's not complex to
> implement because the VM already provide the hook to access to those
> annotations at runtime, @Deprecated is an annotation visible at
> runtime for a good reason, it allows by example to implement policy
> like disallowing or emit a warning when calling a deprecated code at
> runtime.

I completely agree, and the intent of the proposal is to make
annotations on module declarations available at run time -- that's
why it specifically mentions extending the `java.lang.reflect` API.

If there's text in the proposal that suggests otherwise then please
point it out and I'll fix it.  Thanks.

- Mark