Add an "experimental" disclaimer to AnalysisFailureInfo.
In practicality, this has no real effect on documentation, as this type remains undocumented (due to 'documented = false' on the annotation), and the object itself cannot be instantiated, but this ensures that developers reading the source code understand that AnalysisFailureInfo is experimental.
RELNOTES: None.
@@ -26,8 +26,8 @@ import com.google.devtools.build.lib.syntax.SkylarkSemantics.FlagIdentifier;
*/
@SkylarkModule(
name = "AnalysisFailureInfo",
- doc =
- "Encapsulates information about an analysis-phase error which would have occurred during "
+ doc = "<b>Experimental. This API is experimental and subject to change at any time</b><p> "
+ + "Encapsulates information about an analysis-phase error which would have occurred during "
+ "a build. In most builds, an analysis-phase error would result in a build failure "
+ "and the error description would be output to the console. However, if "
+ "<code>--allow_analysis_failure</code> is set, targets which would otherwise fail in "
