on master help sign in
Merge pull request #2478 from jeremy-w/jeremy-w/updates-bst-module-reference-to-Btree
c157e07Jan de Muijnck-Hughes
docs/tutorial/modules.rst+3−3
@@ -34,7 +34,7 @@ module which defines a binary tree type ``BTree`` (in a file
34
34
35
35
36Then, this gives a main program (in a file
36Then, this gives a main program (in a file
37−``bmain.idr``) which uses the ``bst`` module to sort a list:
37+``bmain.idr``) which uses the ``Btree`` module to sort a list:
38
38
39.. code-block:: idris
39.. code-block:: idris
40
40
@@ -50,7 +50,7 @@ Then, this gives a main program (in a file
50
50
51The same names can be defined in multiple modules. This is possible
51The same names can be defined in multiple modules. This is possible
52because in practice names are *qualified* with the name of the module.
52because in practice names are *qualified* with the name of the module.
53−The names defined in the ``btree`` module are, in full:
53+The names defined in the ``Btree`` module are, in full:
54
54
55+ ``Btree.BTree``
55+ ``Btree.BTree``
56+ ``Btree.Leaf``
56+ ``Btree.Leaf``
@@ -99,7 +99,7 @@ and classes to be marked as: ``public``, ``abstract`` or ``private``:
99.. note::
99.. note::
100 If any definition is given an export modifier, then all names with no modifier are assumed to be ``private``.
100 If any definition is given an export modifier, then all names with no modifier are assumed to be ``private``.
101
101
102−For our ``btree`` module, it makes sense for the tree data type and the
102+For our ``Btree`` module, it makes sense for the tree data type and the
103functions to be exported as ``abstract``, as we see below:
103functions to be exported as ``abstract``, as we see below:
104
104
105.. code-block:: idris
105.. code-block:: idris