Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add missing word 'bounded' to definition of flatten #3561

Closed
wants to merge 2 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion specification/dartLangSpec.tex
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,12 @@
% version of the language which will actually be specified by the next stable
% release of this document.
%
% Jan 2024
% - Add the word 'bounded' to a rule in the definition of 'flatten'. This is
% already the implemented behavior, and it is the consistent approach. The
% main consequence is that `await e` will await the future when the static
% type of `e` is, for example, `X extends Future<int>?`.
%
% Dec 2023
% - Allow `~/` on operands of type `double` in constant expressions, aligning
% the specification with already implemented behavior.
Expand Down Expand Up @@ -11746,7 +11752,7 @@ \subsection{Function Expressions}
as follows, using the first applicable case:

\begin{itemize}
\item If $T$ is \code{$S$?}\ for some $S$
\item If $T$ is \code{$S$?}\ bounded for some $S$
then \DefEquals{\flatten{T}}{\code{\flatten{S}?}}.

\item If $T$ is \code{$X$\,\&\,$S$}
Expand Down