jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add link to #6934 in changelog.md

Browse source
This commit is contained in:
Dominik Picheta 2017-12-23 14:08:47 +00:00 • committed by GitHub
commit ca9f3b47d4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
changelog.md
View file

@ -102,10 +102,12 @@ This now needs to be written as:
- Nim's ``rst2html`` command now supports the testing of code snippets via an RST - Nim's ``rst2html`` command now supports the testing of code snippets via an RST
extension that we called ``:test:``:: extension that we called ``:test:``::
```rst
.. code-block:: nim .. code-block:: nim
:test: :test:
# shows how the 'if' statement works # shows how the 'if' statement works
if true: echo "yes" if true: echo "yes"
```
- The ``[]`` proc for strings now raises an ``IndexError`` exception when - The ``[]`` proc for strings now raises an ``IndexError`` exception when
the specified slice is out of bounds. See issue the specified slice is out of bounds. See issue
[#6223](https://github.com/nim-lang/Nim/issues/6223) for more details. [#6223](https://github.com/nim-lang/Nim/issues/6223) for more details.
@ -130,7 +132,8 @@ This now needs to be written as:
- The ``random`` procs in ``random.nim`` have all been deprecated. Instead use - The ``random`` procs in ``random.nim`` have all been deprecated. Instead use
the new ``rand`` procs. The module now exports the state of the random the new ``rand`` procs. The module now exports the state of the random
number generator as type ``Rand`` so multiple threads can easily use their number generator as type ``Rand`` so multiple threads can easily use their
own random number generators that do not require locking. own random number generators that do not require locking. For more information
about this rename see issue [#6934](https://github.com/nim-lang/Nim/issues/6934)
- The compiler is now more consistent in its treatment of ambiguous symbols: - The compiler is now more consistent in its treatment of ambiguous symbols:
Types that shadow procs and vice versa are marked as ambiguous (bug #6693). Types that shadow procs and vice versa are marked as ambiguous (bug #6693).
- ``yield`` (or ``await`` which is mapped to ``yield``) never worked reliably - ``yield`` (or ``await`` which is mapped to ``yield``) never worked reliably