From 04ec0d86c8b43d1cca48adc937b3e596a10577a1 Mon Sep 17 00:00:00 2001
From: Louis Pilfold <louis@lpil.uk>
Date: Tue, 26 Mar 2024 11:36:11 +0000
Subject: Improve introduction of modules and imports

Thanks @RyanBrewer317!
---
 .../chapter0_basics/lesson06_floats/en.html        | 32 ++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 src/content/chapter0_basics/lesson06_floats/en.html

(limited to 'src/content/chapter0_basics/lesson06_floats/en.html')

diff --git a/src/content/chapter0_basics/lesson06_floats/en.html b/src/content/chapter0_basics/lesson06_floats/en.html
new file mode 100644
index 0000000..7175628
--- /dev/null
+++ b/src/content/chapter0_basics/lesson06_floats/en.html
@@ -0,0 +1,32 @@
+<p>Gleam's <code>Float</code> type represents numbers that are not integers.</p>
+<p>
+  Gleam's numerical operators are not overloaded, so there are dedicated
+  operators for working with floats.
+</p>
+<p>
+  Floats are represented as 64 bit floating point numbers on both the Erlang and
+  JavaScript runtimes. The floating point behaviour is native to their
+  respective runtimes, so their exact behaviour will be slightly different
+  on the two runtimes.
+</p>
+<p>
+  Under the JavaScript runtime, exceeding the maximum (or minimum) representable
+  value for a floating point value will result in <code>Infinity</code> (or
+  <code>-Infinity</code>). Should you try to divide two infinities you will
+  get <code>NaN</code> as a result.
+</p>
+<p>
+  When running on the BEAM any overflow will raise an error. So there is
+  no <code>NaN</code> or <code>Infinity</code> float value in the Erlang
+  runtime.
+</p>
+<p>
+  Division by zero will not overflow, but is instead defined to be zero.
+</p>
+<p>
+  The
+  <a href="https://hexdocs.pm/gleam_stdlib/gleam/float.html"
+    ><code>gleam/float</code></a
+  >
+  standard library module contains functions for working with floats.
+</p>
-- 
cgit v1.2.3