cedric
06/26/2016, 2:48 PM@Experimental a satisfying solution since you can't really describe which annotation it applies to (and as a matter of fact, the Javadoc in that source says that all annotations on the class become experimental). I've been wondering about a different approach that might be more drastic: whenever you introduce a new annotation that's experimental, add an attribute experimental to it and force users to set that attribute to true. If they don't, blow up. This makes it clear to everyone that this code is using experimental features.
When the annotation becomes stable, remove experimental, which will cause all the current code to stop compiling, which is also a desired effect.