Merge pull request #2 from RKB1923/65851396_about_nil_master

Learned all about nil in branch 65851396_about_nil_master

[Delivers #65851396]
Fixes 1 being an object on line 5

* 1 as an integer is considered an object

[#65851400]
Fixes 1.5 being an object on line 6

* 1.5 is a floating point and is an object

[#65851400]
Fixes "string" is an object on line 7

* Strings are considered objects

[#65851400]
Fixes nil being an object on line 8

* nil is considered an object, as confirmed in the
  previous exercise.

[#65851400]
Fixes Object being an Object on line 9

* Of course, Object is an Object

[#65851400]
Fixes the integer 123 into a string on line 13

* Integer objects can be turned into strings

[#65851400]
Fixes nil turned into a string on line 14

* This reiterates that turning nil into a string
  makes it equal to ""

[#65851400]
Fixes integer 123 being inspected on line 18

* inspect and to_s do the same thing! I wonder
  why?

[#65851400]
Fixes nil.inspect on line 19

* This is strange. inspect and to_s did the same
  for the integer 123, but for nil, it does
  something different. nil.to_s is the same as "",
  but nil.inspect was not the same as "".
  nil.inspect was the same as "nil"

[#65851400]
Fixes test_every_object_has_an_id on line 24

* This test seems to be saying that the class of
  every object_id is a Fixnum

[#65851400]
Fixes test_every_object_has_different_id

* This test produced 2 new Objects and then
  checked their object_ids for non equality. They
  have different object_ids.

[#65851400]
Fixes false always having the same id on line 34

* false will always have an object id of 0

[#65851400]
Fixes true always having an object id of 20

* true always has an object id of 20. I thought it
  would be a "1." I wonder why this is?

[#65851400]
Fixes nil having an object id of 8

* nil always has an object if of 8. These object
  ids are not intuitive

[#65851400]
Fixes 0 having an object id of 1

* 0 always has an object id of 1

[#65851400]
Fixes 1 having an object id of 3

* 1 always has an object id of 3

[#65851400]
Fixes 2 having an object id of 5

* 2 always has an object id of 5

[#65851400]
Fixes 100 having an object id of 201

* 100 always has an object_id of 201. It seems
  that small integers have a pattern of:
  (value * 2) + 1

[#65851400]
Fixes comparing an object and its clone on line 53

* When invoking the clone method on an object, it
  created as new object.

[#65851400]