------------------
This release breaks backward-compatibility. Previously, if arrays were fed into
NumPy functions, an attempt would be made to densify the array and apply the NumPy
function. This was unintended behaviour in most cases, with the array filling up
memory before raising a ``MemoryError`` if the array was too large.
We have now changed this behaviour so that a ``RuntimeError`` is now raised if
an attempt is made to automatically densify an array. To densify, use the explicit
``.todense()`` method.
* Fixed a bug where ``np.matrix`` could sometimes fail to
convert to a ``COO``. (Issue [199](https://github.com/pydata/sparse/issues/199), PR [#200](https://github.com/pydata/sparse/pull/200)).
* Make sure that ``sparse sparse`` returns a sparse array. (Issue [201](https://github.com/pydata/sparse/issues/201), PR [#203](https://github.com/pydata/sparse/pull/203))
* Bring ``operator.matmul`` behaviour in line with NumPy for ``ndim > 2``.
(Issue [202](https://github.com/pydata/sparse/issues/202), PR [#204](https://github.com/pydata/sparse/pull/204), PR [#217](https://github.com/pydata/sparse/pull/217))
* Make sure ``dtype`` is preserved with the ``out`` kwarg. (Issue [205](https://github.com/pydata/sparse/issues/205), PR [#206](https://github.com/pydata/sparse/pull/206))
* Fix integer overflow in ``reduce`` on Windows. (Issue [207](https://github.com/pydata/sparse/issues/207), PR [#208](https://github.com/pydata/sparse/pull/208))
* Disallow auto-densification. (Issue [218](https://github.com/pydata/sparse/issues/218), PR [#220](https://github.com/pydata/sparse/pull/220))
* Add auto-densification configuration, and a configurable warning for checking
if the array is too dense. (PR [210](https://github.com/pydata/sparse/pull/210), PR [#213](https://github.com/pydata/sparse/pull/213))
* Add pruning of fill-values to COO constructor. (PR [221](https://github.com/pydata/sparse/pull/221))