You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorials/01_fp-env.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,7 +114,7 @@ Haskell does not require a specific editor or IDE. You can use any editor you ar
114
114
115
115
Common choices include:
116
116
117
-
***Vim** with [Haskell plugins](https://wiki.haskell.org/Vim) for command-line enthusiasts
117
+
***Vim** with [Haskell plugins](https://wiki.haskell.org/Vim) for command-line enthusiasts
118
118
***Visual Studio Code** with [Haskell extension](https://marketplace.visualstudio.com/items?itemName=haskell.haskell) for a modern and user-friendly experience
119
119
***IntelliJ IDEA** with [Haskell LSP](https://plugins.jetbrains.com/plugin/24123-haskell-lsp) for those who prefer JetBrains IDEs
120
120
***Emacs** with [Haskell mods](https://wiki.haskell.org/Emacs) for Emacs lovers
Copy file name to clipboardExpand all lines: tutorials/02_functions-types.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ In this tutorial, we build on that foundation and make the picture more concrete
11
11
12
12
* how functions are written and typed,
13
13
* how Haskell represents data, and
14
-
*how syntax reflects the underlying functional and mathematical model.
14
+
*how syntax reflects the underlying functional and mathematical model.
15
15
16
16
Before diving into functions and data types themselves, it is useful to clarify some basic syntactic rules and naming conventions that appear throughout Haskell code. This part is not meant to be memorized — it is a reference that will become familiar as we encounter these constructs in practice.
17
17
@@ -144,7 +144,7 @@ z = (x + 7) :: Integer
144
144
Haskell uses static typing:
145
145
146
146
* every expression has exactly one type,
147
-
*the type is determined at compile time, and
147
+
*the type is determined at compile time, and
148
148
* it cannot change during execution.
149
149
150
150
Because of **type inference**, type signatures are not always required, but they are **strongly recommended for clarity and documentation**.
@@ -324,7 +324,7 @@ Haskell provides a small set of basic data types that are used throughout the st
324
324
*`Double` = double-precision floating point
325
325
*`Word` = unsigned integer
326
326
*`Char` = Unicode character
327
-
*`Bool` = logical value (`True¨ or `False`)
327
+
*`Bool` = logical value (`True` or `False`)
328
328
*`String` = type synonym for `[Char]` (list of characters)
329
329
330
330
You have already encountered most of these in GHCi examples. More specialized data structures (maps, sets, sequences, text) live in libraries and will be introduced when needed.
@@ -393,7 +393,7 @@ data Pet = Pet
393
393
394
394
There are several ways to address this:
395
395
396
-
* use more specific field names (personName, petName),
396
+
* use more specific field names (`personName`, `petName`),
397
397
* use modules to separate namespaces,
398
398
*or enable language extensions such as `DuplicateRecordFields`.
399
399
@@ -521,7 +521,7 @@ addFirstTwo (x, y, _) = x + y
521
521
522
522
#### Tuples as product types
523
523
524
-
Conceptually, tuples are **product types*. A tuple `(a, b)` contains both an `a` and a `b`.
524
+
Conceptually, tuples are **product types**. A tuple `(a, b)` contains both an `a` and a `b`.
0 commit comments