Created a subsection on equality.

hasselg · hasselg · commit 7bd2a0f74b57 · 2014-04-17T22:19:17.000-04:00
Created a new page beginning to discuss equality early on, immediately after types. This introduces == and === operators as soon as can be done (IMO) after types are introduced.
diff --git a/SUMMARY.md b/SUMMARY.md
@@ -4,6 +4,7 @@
     * [Comments](basics/comments.md)
     * [Variables](basics/variables.md)
     * [Types](basics/types.md)
+    * [Equality](basics/equality.md)
 * [Numbers](numbers/README.md)
     * [Creation](numbers/create.md)
     * [Basic Operators](numbers/operators.md)
diff --git a/basics/equality.md b/basics/equality.md
@@ -0,0 +1,18 @@
+# Equality
+
+Programmers frequently need to determine the equality of variables in relation to other variables. This is done using an equality operator.
+
+The most basic equality operator is the `==` operator. This operator does everything it can to make determine if two variables are equal, even if they are not of the same type. 
+
+For example, assume
+```
+var foo = 42;
+var bar = 42;
+var baz = "42";
+var qux = "life";
+```
+.
+
+`foo == bar` will evaluate to `true` and `baz == qux` will evaluate to false, as one would expect. However, `foo == baz` will *also* evaluate to `true` despite `foo` and `baz` being different types. Behind the scenes the `==` equality operator attempts to force its operands to the same type before determining their equality. This is in contrast to the `===` equality operator.
+
+The `===` equality operator determines that two variables are equal if they are of the same type *and* have the same value. With the same assumptions as before, this means that `foo === bar` will still evaluate to `true`,  but `foo === baz` will now evaluate to `false`. `baz === qux` will still evaluate to `false`.
