Add @visibleForTesting annotation to meta.

pkg/meta/lib/meta.dart

Index: pkg/meta/lib/meta.dart
diff --git a/pkg/meta/lib/meta.dart b/pkg/meta/lib/meta.dart
index 99a3924683d74e9aa7e2014f28350b92e86d901c..f69837f8144f249b7dd5a6af4cafda94ca63f5f6 100644
--- a/pkg/meta/lib/meta.dart
+++ b/pkg/meta/lib/meta.dart
@@ -97,6 +97,18 @@ const _Protected protected = const _Protected();
 ///   corresponding to a named parameter that has this annotation.
 const Required required = const Required();
 
+/// Used to annotate an element was made public, so that it is more visible
+/// than otherwise necessary, to make code testable.

[Brian Wilkerson, 2016/08/10 20:17:56]

I've generally tried to word comments without using analyzer-specific terms like
"element". Perhaps something like:

   Used to annotate a declaration that was made public in order to make it
visible to test code.

and then replace "element" with "declaration" in the two places it's used below.

[scheglov, 2016/08/10 20:21:56]

Done.

+///
+/// Tools, such as the analyzer, can provide feedback if
+///
+/// * the annotation is associated with an element not in the `lib` folder
+///   of a package;
+///   or
+/// * the element is referenced outside of its the defining library or a library
+///   which is in the `test` folder of the defining package.
+const _VisibleForTesting visibleForTesting = const _VisibleForTesting();
+
 /// Used to annotate a named parameter `p` in a method or function `f`.
 ///
 /// See [required] for more details.
@@ -135,3 +147,7 @@ class _OptionalTypeArgs {
 class _Protected {
   const _Protected();
 }
+
+class _VisibleForTesting {
+  const _VisibleForTesting();
+}