Maintainance

[vadixidav]

Closes #14, closes #16.

Remove patch version dependence. Note: This may violate semver, but is highly requested.

Use GAT lifetimes to simplify traits.

Rename traits and methods to be in-line with Rust idioms.

Use new dependency feature flag capabilities in Cargo to properly handle dependencies and alloc feature.

Simplify some implementations.

Fix up documentation to match changes.

Add some information to the README.

[tnibler]

Remove patch version dependence. Note: This may violate semver, but is highly requested.

I don't think it does (but correct me if I'm wrong), if the dependencies follow semver, they won't break public APIs in patch or minor versions (though I'm not sure how minor versions and 0.x numbers interact. So I think it's fine and this package is not doing anything wrong this way.

[xd009642]

Honestly with the patch stuff cargo can actually update the patch version unless you've specified it as "=0.x.y" which stops it from updating. I think most people complaining about patch versions are trying to use versions with a different minor version (which won't get auto updated for a 0.x crate because it treats the minor like a major version then

[tnibler]

Ahh right my bad. Well I'd hope image and ndarray don't break their literal core types all that often so it'll probably be fine ;)

[vadixidav]

It seems Cargo does allow the patch version to change by default, but according to the actual semver specification there is no guarantee of compatibility for any 0.x.y release. I think in the Rust community it is probably correct to simply assume that 0.x.y is essentially x - major and y - minor version.