diff options
author | Louis Pilfold <louis@lpil.uk> | 2024-01-04 20:06:40 +0000 |
---|---|---|
committer | Louis Pilfold <louis@lpil.uk> | 2024-01-04 20:06:40 +0000 |
commit | 09a8a96664fadbc2933024910b95526f7d66843f (patch) | |
tree | e079fe2f9979af4fb4e22b18652ae3a3d876ffa3 /src/content/chapter5_advance_features | |
parent | 51a1fcbd0e42b25238877d3ad05d1690e8bc1553 (diff) | |
download | tour-09a8a96664fadbc2933024910b95526f7d66843f.tar.gz tour-09a8a96664fadbc2933024910b95526f7d66843f.zip |
More content!
Diffstat (limited to 'src/content/chapter5_advance_features')
4 files changed, 47 insertions, 0 deletions
diff --git a/src/content/chapter5_advance_features/lesson00_todo/code.gleam b/src/content/chapter5_advance_features/lesson00_todo/code.gleam new file mode 100644 index 0000000..d5abe8f --- /dev/null +++ b/src/content/chapter5_advance_features/lesson00_todo/code.gleam @@ -0,0 +1,7 @@ +pub fn main() { + todo as "I haven't written this code yet!" +} + +pub fn todo_without_reason() { + todo +} diff --git a/src/content/chapter5_advance_features/lesson00_todo/text.html b/src/content/chapter5_advance_features/lesson00_todo/text.html new file mode 100644 index 0000000..4a2c433 --- /dev/null +++ b/src/content/chapter5_advance_features/lesson00_todo/text.html @@ -0,0 +1,14 @@ +<p> + The <code>todo</code> keyword is used to specify that some code is not yet + implemented. +</p> +<p> + The <code>as "some string"</code> is optional, though you may wish to include + the message if you have more than one code block marked as + <code>todo</code> in your code. +</p> +<p> + When used the Gleam compiler will print a warning to remind you the code is + unfinished, and if the code is run then the program will crash with the given + message. +</p> diff --git a/src/content/chapter5_advance_features/lesson01_panic/code.gleam b/src/content/chapter5_advance_features/lesson01_panic/code.gleam new file mode 100644 index 0000000..fce9d66 --- /dev/null +++ b/src/content/chapter5_advance_features/lesson01_panic/code.gleam @@ -0,0 +1,15 @@ +import gleam/io + +pub fn main() { + print_score(10) + print_score(100_000) + print_score(-1) +} + +pub fn print_score(score: Int) { + case score { + score if score > 1000 -> io.println("High score!") + score if score > 0 -> io.println("Still working on it") + _ -> panic as "Scores should never be negative!" + } +} diff --git a/src/content/chapter5_advance_features/lesson01_panic/text.html b/src/content/chapter5_advance_features/lesson01_panic/text.html new file mode 100644 index 0000000..843a65b --- /dev/null +++ b/src/content/chapter5_advance_features/lesson01_panic/text.html @@ -0,0 +1,11 @@ +<p> + The <code>panic</code> keyword is similar to <code>todo</code> keyword, but it + is used to crash the program when the program has reached a point that should + never be reached. +</p> +<p> + This keyword should almost never be used! It may be useful in initial + prototypes and scripts, but its use in a library or production application is + a sign that the design could be improved. With well designed types the type + system can typically be used to make these invalid states unrepresentable. +</p> |