spec: be explicit that NRVO will evolve further
This commit is contained in:
parent
984af3d64e
commit
177c7f96e9
1 changed files with 4 additions and 0 deletions
|
|
@ -3714,6 +3714,10 @@ location is derived from the second parameter (called
|
||||||
NRVO
|
NRVO
|
||||||
----
|
----
|
||||||
|
|
||||||
|
**Note**: This section describes the current implementation. This part
|
||||||
|
of the language specification will be changed.
|
||||||
|
See https://github.com/nim-lang/RFCs/issues/230 for more information.
|
||||||
|
|
||||||
The return value is represented inside the body of a routine as the special
|
The return value is represented inside the body of a routine as the special
|
||||||
`result`:idx: variable. This allows for a mechanism much like C++'s
|
`result`:idx: variable. This allows for a mechanism much like C++'s
|
||||||
"named return value optimization" (`NRVO`:idx:). NRVO means that the stores
|
"named return value optimization" (`NRVO`:idx:). NRVO means that the stores
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue