RST backtick refactor (all *.rst except manual.rst and rst_examples.rst) (#17258)
Co-authored-by: quantimnot <quantimnot@users.noreply.github.com>
This commit is contained in:
parent
15586c7a7a
commit
83ae70cb54
30 changed files with 1402 additions and 1350 deletions
|
|
@ -1,6 +1,8 @@
|
|||
Memory safety for returning by ``var T`` is ensured by a simple borrowing
|
||||
rule: If ``result`` does not refer to a location pointing to the heap
|
||||
(that is in ``result = X`` the ``X`` involves a ``ptr`` or ``ref`` access)
|
||||
.. default-role:: code
|
||||
|
||||
Memory safety for returning by `var T` is ensured by a simple borrowing
|
||||
rule: If `result` does not refer to a location pointing to the heap
|
||||
(that is in `result = X` the `X` involves a `ptr` or `ref` access)
|
||||
then it has to be derived from the routine's first parameter:
|
||||
|
||||
.. code-block:: nim
|
||||
|
|
@ -11,10 +13,10 @@ then it has to be derived from the routine's first parameter:
|
|||
var x: int
|
||||
# we know 'forward' provides a view into the location derived from
|
||||
# its first argument 'x'.
|
||||
result = forward(x) # Error: location is derived from ``x``
|
||||
result = forward(x) # Error: location is derived from `x`
|
||||
# which is not p's first parameter and lives
|
||||
# on the stack.
|
||||
|
||||
In other words, the lifetime of what ``result`` points to is attached to the
|
||||
In other words, the lifetime of what `result` points to is attached to the
|
||||
lifetime of the first parameter and that is enough knowledge to verify
|
||||
memory safety at the call site.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue