Skip to content

Adjust 'Type Aliases' to outlaw explicit type arguments in static method call #1672

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 8, 2021
Merged

Adjust 'Type Aliases' to outlaw explicit type arguments in static method call #1672

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
26 changes: 14 additions & 12 deletions specification/dartLangSpec.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,8 @@
% publishing a stable version of the specification).
% - Add rule that a top-level pair of declarations with the same basename
% is a compile-time error except when it is a getter/setter pair.
% - Change grammar to enable non-function type aliases. Correct rule for
% invoking `F.staticMethod()` where `F` is a type alias.
%
% 2.8 - 2.10
% - Change several warnings to compile-time errors, matching the actual
Expand Down Expand Up @@ -20117,10 +20119,9 @@ \subsection{Type Aliases}
because of the prominent occurrence of the token \TYPEDEF.%
}

%%TODO(eernst): With non-function type aliases, change <functionType> to <type>.
\begin{grammar}
<typeAlias> ::= \gnewline{}
\TYPEDEF{} <typeIdentifier> <typeParameters>? `=' <functionType> `;'
\TYPEDEF{} <typeIdentifier> <typeParameters>? `=' <type> `;'
\alt \TYPEDEF{} <functionTypeAlias>

<functionTypeAlias> ::= <functionPrefix> <formalParameterPart> `;'
Expand Down Expand Up @@ -20333,23 +20334,24 @@ \subsection{Type Aliases}
\code{\TYPEDEF{} $F$<\TypeParametersStd> = $T$;}

\noindent
and let \DefineSymbol{U} be a parameterized type of the form
\code{$F$<\List{U}{1}{s}>}
in a scope where $F$ denotes $D$.
Assume that the transitive alias expansion of $U$ is
a type of the form $C$ or \code{$p$.$C$}
where $C$ is an identifier denoting a class or mixin,
and $p$ is an identifier denoting an import prefix,
optionally followed by \synt{typeArguments}.
and let \DefineSymbol{U} be a type of the form $F$ or \code{$p$.$F$}
in a scope where this term denotes $D$.
Assume that the transitive alias expansion of \code{$F$<\List{X}{1}{s}>} is
\BlindDefineSymbol{C, q}%
a type of the form $C$ or \code{$q$.$C$},
optionally followed by \synt{typeArguments},
where $q$ is an identifier denoting an import prefix,
and $C$ respectively \code{$q$.$C$} denotes a class or mixin
(\commentary{in particular, $C$ can not be a type variable}).
Assume that $U$ occurs in an expression $e$ of the form
`\code{$U$.\id\;\metavar{args}}'
where \metavar{args} is derived from \syntax{<argumentPart>?},
such that \id{} is the name of
a static member of $C$ respectively \code{$p$.$C$}.
a static member of $C$ respectively \code{$q$.$C$}.
The expression $e$ is then treated as
`\code{$C$.\id\;\metavar{args}}'
respectively
`\code{$p$.$C$.\id\;\metavar{args}}'.
`\code{$q$.$C$.\id\;\metavar{args}}'.

\commentary{%
This means that it is possible to use a type alias
Expand Down