Revert to Laravel namespace?

[Isinlor]

It's not an official Laravel package so we don't want to use the Packagist namespace reserved by Laravel packages. One day Collection may be extracted from illuminate/support to a new package. If so, we'll deprecate this package and point to the core version.

The issues seem like pretty good reason to ignore courtesy and go with Laravel namespace.
#104
#90

Was there any technical reason to change namespace?

Packagist should be fine with package named NotLaravel/Collection delivering classes from Laravel namespace. I would also expect php/composer autoloader to handle loading of classes duplicate in multiple files without issues. Either of them would be loaded first and the other ignored.

The only issue should be keeping 100% consistency with Laravel versioning.

[mattstauffer]

#54

See this issue and its corresponding PRs.