Make it explicit that "dynamic" is exported from dart:core.
Change-Id: I15a0716fdfe83da248dc4380d5550318f80a1c98
Reviewed-on: https://dart-review.googlesource.com/25420
Commit-Queue: Lasse R.H. Nielsen <lrn@google.com>
Reviewed-by: Erik Ernst <eernst@google.com>
Reviewed-by: Leaf Petersen <leafp@google.com>
diff --git a/docs/language/dartLangSpec.tex b/docs/language/dartLangSpec.tex
index bad2ba0..502333c 100644
--- a/docs/language/dartLangSpec.tex
+++ b/docs/language/dartLangSpec.tex
@@ -61,6 +61,7 @@
% - Add appendix listing the major differences between 64-bit integers
% and JavaScript integers.
% - Remove appendix on naming conventions.
+% - Make it explicit that "dynamic" is exported from dart:core.
%
% 1.15
% - Change how language specification describes control flow.
@@ -10051,7 +10052,10 @@
}
\LMHash{}
-The name \DYNAMIC{} denotes a \code{Type} object even though \DYNAMIC{} is not a class.
+The built-in type declaration \code{dynamic},
+which is declared in the library \code{dart:core},
+denotes the \DYNAMIC{} type.
+When the name \DYNAMIC{} exported by \code{dart:core} is evaluated as an expression, it evaluates to a \code{Type} object representing the \DYNAMIC{} type, even though \DYNAMIC{} is not a class.
\LMHash{}
The built-in type declaration \code{FutureOr},
