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

workaround #17091: manual.rst now renders as RST in github (#17092)

Browse source
This commit is contained in:
Timothee Cour 2021-02-19 06:35:34 -08:00 • committed by GitHub
commit 1018f51fce
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/manual.rst
View file

@ -5884,7 +5884,7 @@ This is best illustrated by an example:
Import statement Import statement
~~~~~~~~~~~~~~~~ ----------------
After the ``import`` statement, a list of module names can follow or a single After the ``import`` statement, a list of module names can follow or a single
module name followed by an ``except`` list to prevent some symbols from being module name followed by an ``except`` list to prevent some symbols from being
@ -5908,7 +5908,8 @@ The ``import`` statement is only allowed at the top level.
Include statement Include statement
~~~~~~~~~~~~~~~~~ -----------------
The ``include`` statement does something fundamentally different than The ``include`` statement does something fundamentally different than
importing a module: it merely includes the contents of a file. The ``include`` importing a module: it merely includes the contents of a file. The ``include``
statement is useful to split up a large module into several files: statement is useful to split up a large module into several files:
@ -5931,7 +5932,7 @@ The ``include`` statement can be used outside of the top level, as such:
Module names in imports Module names in imports
~~~~~~~~~~~~~~~~~~~~~~~ -----------------------
A module alias can be introduced via the ``as`` keyword: A module alias can be introduced via the ``as`` keyword:
@ -5961,7 +5962,7 @@ Likewise, the following does not make sense as the name is ``strutils`` already:
Collective imports from a directory Collective imports from a directory
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -----------------------------------
The syntax ``import dir / [moduleA, moduleB]`` can be used to import multiple modules The syntax ``import dir / [moduleA, moduleB]`` can be used to import multiple modules
from the same directory. from the same directory.
@ -5974,7 +5975,7 @@ name is not a valid Nim identifier it needs to be a string literal:
Pseudo import/include paths Pseudo import/include paths
~~~~~~~~~~~~~~~~~~~~~~~~~~~ ---------------------------
A directory can also be a so-called "pseudo directory". They can be used to A directory can also be a so-called "pseudo directory". They can be used to
avoid ambiguity when there are multiple modules with the same path. avoid ambiguity when there are multiple modules with the same path.
@ -5991,7 +5992,7 @@ library locations*. In other words, it is the opposite of ``std``.
From import statement From import statement
~~~~~~~~~~~~~~~~~~~~~ ---------------------
After the ``from`` statement, a module name follows followed by After the ``from`` statement, a module name follows followed by
an ``import`` to list the symbols one likes to use without explicit an ``import`` to list the symbols one likes to use without explicit
@ -6012,7 +6013,7 @@ in ``module``.
Export statement Export statement
~~~~~~~~~~~~~~~~ ----------------
An ``export`` statement can be used for symbol forwarding so that client An ``export`` statement can be used for symbol forwarding so that client
modules don't need to import a module's dependencies: modules don't need to import a module's dependencies: