on master help sign in
Fixed typo in typesfuns.rst
commite3ddce1267943ff4ce00983ef084d8af92355a21 authorJan de Muijnck-Hughes <jfdm@st-andrews.ac.uk> dateMon 12 Sep 2016, 09:17 (10 years ago) parent6291a3f
1 file changed+3−2
docs/tutorial/typesfuns.rst+3−2
docs/tutorial/typesfuns.rst+3−2
@@ -469,7 +469,7 @@ It is a matter of taste whether you want to do this — sometimes it can
469469help document a function by making the purpose of an argument more
470470clear.
471471
472−Furthermore, ``{}`` can be used to pattern match on the left hand side, i.e.
472+Furthermore, ``{}`` can be used to pattern match on the left hand side, i.e.
473473``{var = pat}`` gets an implicit variable and attempts to pattern match on "pat";
474474For example :
475475
@@ -1074,7 +1074,7 @@ The syntax ``record { field = val, ... }`` generates a function which
10741074updates the given fields in a record. ``=`` assigns a new value to a field,
10751075and ``$=`` applies a function to update its value.
10761076
1077−Each record is defined in its own namespace, which means that field names
1077+Each record is defined in its own namespace, which means that field names
10781078can be reused in multiple records.
10791079
10801080Records, and fields within records, can have dependent types. Updates
@@ -1331,6 +1331,7 @@ at runtime if called on an empty list. (This is similar to the behavior of
13311331Haskell's ``head`` function.) ``unsafeHead`` might look like this:
13321332
13331333.. code-block:: idris
1334+
13341335 -- Unsafe head example!
13351336 unsafeHead : List a -> a
13361337 unsafeHead (x::xs) = x