bugfix: internal error in evalFieldAccess; parseutils.interpolatedFragments optimized; tstringinterp.nim now works
This commit is contained in:
parent
0f37d0e1f2
commit
14968fba46
10 changed files with 119 additions and 126 deletions
|
|
@ -3405,9 +3405,9 @@ exception in one thread terminates the whole *process*!
|
|||
Taint mode
|
||||
==========
|
||||
|
||||
The Nimrod compiler and standard library support a `taint mode`:idx:.
|
||||
Input strings are declared with the `TaintedString`:idx: string type declared
|
||||
in the ``system`` module.
|
||||
The Nimrod compiler and most parts of the standard library support
|
||||
a `taint mode`:idx:. Input strings are declared with the `TaintedString`:idx:
|
||||
string type declared in the ``system`` module.
|
||||
|
||||
If the taint mode is turned on (via the ``--taintMode:on`` command line
|
||||
option) it is a distinct string type which helps to detect input
|
||||
|
|
@ -3423,4 +3423,3 @@ validation errors:
|
|||
If the taint mode is turned off, ``TaintedString`` is simply an alias for
|
||||
``string``.
|
||||
|
||||
|
||||
|
|
|
|||
10
doc/tut1.txt
10
doc/tut1.txt
|
|
@ -583,6 +583,16 @@ allow to silently throw away a return value:
|
|||
discard yes("May I ask a pointless question?")
|
||||
|
||||
|
||||
The return value can be ignored implicitely if the called proc/iterator has
|
||||
been declared with the ``discardable`` pragma:
|
||||
|
||||
.. code-block:: nimrod
|
||||
proc p(x, y: int): int {.discardable.} =
|
||||
return x + y
|
||||
|
||||
p(3, 4) # now valid
|
||||
|
||||
|
||||
Named arguments
|
||||
---------------
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue