The actual change to the wording of `assert` that I intended in the previous CL.

docs/language/dartLangSpec.tex

Index: docs/language/dartLangSpec.tex
diff --git a/docs/language/dartLangSpec.tex b/docs/language/dartLangSpec.tex
index d717980b38f336159330eef7bb8e4abc0a2c5324..0b87147626a3076941b2f9911ef2f60a4908377b 100644
--- a/docs/language/dartLangSpec.tex
+++ b/docs/language/dartLangSpec.tex
@@ -6774,17 +6774,12 @@ execution of an assertion \code{\ASSERT{}($c$, $e$)} proceeds as follows:
 
 \LMHash{}
 The expression $c$ is evaluated to an object $o$.
-If the class of $o$ is not a subtype of \code{Function} then
-let $r$ be $o$.
-Otherwise,
-if the assertion occurs in the initializer list of a \CONST{} constructor,
-then we say that the assertion failed,
-otherwise let $r$ be the result of invoking $o$ with no arguments.
-It is a dynamic type error if $o$ is not of type \code{bool} or of type \code{Function}, or if $r$ is not of type \code{bool}.
-If $r$ is \FALSE{}, we say that the assertion failed.
-If $r$ is \TRUE{}, we say that the assertion succeeded.
-If the assertion succeeded, execution of the assert statement completes normally (\ref{completion}).
-If the assertion failed, $e$ is evaluated to an object $m$.
+If the class of $o$ is a subtype of \code{Function} and assertion occurs in the initializer list of a \CONST{} constructor,

[eernst, 2017/07/10 13:03:58]

Typo: `and [the] assertion`.

But I don't get this at all: The informal spec talks about allowing `assert` in
the initializer list of generative constructors, and they may or may not be
const. For a const constructor I'd expect that the 'condition and message
expressions in the assert must be potentially compile-time constant expressions'
which may or may not be true for that function (a static function is ok, a
function literal isn't). As a second step, we consider a specific const
constructor invocation, and that invocation will then give rise to the const
evaluation which cannot include a function call.

For a non-const instance creation expression invoking said const constructor I
would expect the function to get called (letting '$r$ be the result of invoking
$o$ with no arguments').

+then let $r$ be the result of invoking $o$ with no arguments.
+Otherwise let $r$ be $o$.
+It is a dynamic type error if $r$ is not of type \code{bool}.
+If $r$ is \TRUE{}, execution of the assert statement completes normally (\ref{completion}).
+Otherwise, $e$ is evaluated to an object $m$.
 Then the execution of the assert statement throws (\ref{completion}) an \code{AssertionError} containing $m$ and with a stack trace corresponding to the current execution state at the \ASSERT{} statement.
 
 \LMHash{}