keep casing of noinit and noreturn pragmas consistently documented (#19535)
This commit is contained in:
parent
30e9f23ec0
commit
f019e999d4
1 changed files with 2 additions and 2 deletions
|
|
@ -2818,7 +2818,7 @@ The implicit initialization can be avoided for optimization reasons with the
|
||||||
|
|
||||||
.. code-block:: nim
|
.. code-block:: nim
|
||||||
var
|
var
|
||||||
a {.noInit.}: array[0..1023, char]
|
a {.noinit.}: array[0..1023, char]
|
||||||
|
|
||||||
If a proc is annotated with the `noinit` pragma, this refers to its implicit
|
If a proc is annotated with the `noinit` pragma, this refers to its implicit
|
||||||
`result` variable:
|
`result` variable:
|
||||||
|
|
@ -6636,7 +6636,7 @@ but accessed at runtime:
|
||||||
doAssert nameToProc[2][1]() == "baz"
|
doAssert nameToProc[2][1]() == "baz"
|
||||||
|
|
||||||
|
|
||||||
noReturn pragma
|
noreturn pragma
|
||||||
---------------
|
---------------
|
||||||
The `noreturn` pragma is used to mark a proc that never returns.
|
The `noreturn` pragma is used to mark a proc that never returns.
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue