mirror of
https://github.com/luau-lang/luau.git
synced 2025-05-04 10:33:46 +01:00
Tidying up
This commit is contained in:
parent
1edb6a6e9e
commit
3cfad6c692
2 changed files with 3 additions and 3 deletions
Binary file not shown.
|
@ -167,8 +167,8 @@ prohibitively expensive.
|
|||
|
||||
The difficult part of non-strict mode error-reporting is predicting
|
||||
run-time errors. We do this using an error-reporting
|
||||
pass that synthesizes a type context such that if any of the $x : T$ in
|
||||
the type context are satisfied, then the program will
|
||||
pass that synthesizes a type context $\Delta$ such that if any of the $x : T$ in
|
||||
$\Delta$ are satisfied, then the program will
|
||||
produce a type error. For example in the program
|
||||
\begin{verbatim}
|
||||
function h(x, y)
|
||||
|
@ -335,7 +335,7 @@ we call any function of type
|
|||
(S \fun T) \cap (\neg S \fun \ERROR)
|
||||
\]
|
||||
a \emph{checked} function, since it performs a run-time check
|
||||
on its argument. They are called \emph{strong functions}
|
||||
on its argument. They are called \emph{strong arrows}
|
||||
in Elixir~\cite{DesignElixir}.
|
||||
|
||||
Note that this type system has the usual subtyping rule for
|
||||
|
|
Loading…
Add table
Reference in a new issue