mirror of
https://github.com/nim-lang/Nim.git
synced 2026-01-05 20:47:53 +00:00
removing out T from docs since it no longer working (#16378) [backport]
* remove `out T` from docs see https://github.com/nim-lang/Nim/issues/16131 * remove `out T` in title * remove entire paragraph
This commit is contained in:
@@ -2499,13 +2499,13 @@ matches) is preferred:
|
||||
gen(ri) # "ref T"
|
||||
|
||||
|
||||
Overloading based on 'var T' / 'out T'
|
||||
Overloading based on 'var T'
|
||||
--------------------------------------
|
||||
|
||||
If the formal parameter ``f`` is of type ``var T`` (or ``out T``)
|
||||
in addition to the ordinary
|
||||
type checking, the argument is checked to be an `l-value`:idx:.
|
||||
``var T`` (or ``out T``) matches better than just ``T`` then.
|
||||
If the formal parameter ``f`` is of type ``var T``
|
||||
in addition to the ordinary type checking,
|
||||
the argument is checked to be an `l-value`:idx:.
|
||||
``var T`` matches better than just ``T`` then.
|
||||
|
||||
.. code-block:: nim
|
||||
proc sayHi(x: int): string =
|
||||
@@ -2524,17 +2524,6 @@ type checking, the argument is checked to be an `l-value`:idx:.
|
||||
# 13
|
||||
|
||||
|
||||
An l-value matches ``var T`` and ``out T`` equally well, hence
|
||||
the following is ambiguous:
|
||||
|
||||
.. code-block:: nim
|
||||
|
||||
proc p(x: out string) = x = ""
|
||||
proc p(x: var string) = x = ""
|
||||
var v: string
|
||||
p(v) # ambiguous
|
||||
|
||||
|
||||
Lazy type resolution for untyped
|
||||
--------------------------------
|
||||
|
||||
@@ -4975,7 +4964,7 @@ of "typedesc"-ness is stripped off:
|
||||
Generic inference restrictions
|
||||
------------------------------
|
||||
|
||||
The types ``var T``, ``out T`` and ``typedesc[T]`` cannot be inferred in a generic
|
||||
The types ``var T`` and ``typedesc[T]`` cannot be inferred in a generic
|
||||
instantiation. The following is not allowed:
|
||||
|
||||
.. code-block:: nim
|
||||
@@ -6155,10 +6144,10 @@ noSideEffect pragma
|
||||
The ``noSideEffect`` pragma is used to mark a proc/iterator to have no side
|
||||
effects. This means that the proc/iterator only changes locations that are
|
||||
reachable from its parameters and the return value only depends on the
|
||||
arguments. If none of its parameters have the type ``var T`` or ``out T``
|
||||
or ``ref T`` or ``ptr T`` this means no locations are modified. It is a static
|
||||
error to mark a proc/iterator to have no side effect if the compiler cannot
|
||||
verify this.
|
||||
arguments. If none of its parameters have the type ``var T`` or ``ref T``
|
||||
or ``ptr T`` this means no locations are modified. It is a static error to
|
||||
mark a proc/iterator to have no side effect if the compiler cannot verify
|
||||
this.
|
||||
|
||||
As a special semantic rule, the built-in `debugEcho
|
||||
<system.html#debugEcho,varargs[typed,]>`_ pretends to be free of side effects,
|
||||
|
||||
Reference in New Issue
Block a user