Move contract on Enumerable

It doesn't really makes sense that Enumerable is also array accesible or has anything to do with JSON manipulations. These interfaces should be defined on the implementing class.

It does makes sense however to keep Countable and IteratorAggregate as we're still talking about collections here. But we shouldn't force people to also implement ArrayAccess or also any JSON contracts.

Author: driesvints

src/Illuminate/Collections/Enumerable.php

@@ -3,12 +3,9 @@
 namespace Illuminate\Collections;
 
 use Countable;
-use Illuminate\Contracts\Support\Arrayable;
-use Illuminate\Contracts\Support\Jsonable;
 use IteratorAggregate;
-use JsonSerializable;
 
-interface Enumerable extends Arrayable, Countable, IteratorAggregate, Jsonable, JsonSerializable
+interface Enumerable extends Countable, IteratorAggregate
 {
     /**
      * Create a new collection instance if the value isn't one already.

src/Illuminate/Collections/LazyCollection.php

@@ -4,11 +4,14 @@
 
 use ArrayIterator;
 use Closure;
+use Illuminate\Contracts\Support\Arrayable;
+use Illuminate\Contracts\Support\Jsonable;
 use Illuminate\Macroable\Macroable;
 use IteratorAggregate;
+use JsonSerializable;
 use stdClass;
 
-class LazyCollection implements Enumerable
+class LazyCollection implements Arrayable, Enumerable, Jsonable, JsonSerializable
 {
     use EnumeratesValues, Macroable;