0.1.0

This will be the last release under rust edition 2018. In addition to bumping to edition 2021, we also want to settle issues 17-26 before minting 1.0. From this point until 1.0 we'll use minor version numbers to indicate API changes and patch numbers for other updates

What's Changed

• removed most uses of clone
• documented remaining uses of clone and other allocations
• changed retain's signature to use an owned usize
• add custom type alias to avoid leaking implementation types
• changed get to return value instead of reference
• update of all deps, minimum verisons, and testing images
• and more!

Full Changelog: 0.0.4...0.1.0

0.0.4

Over 50 fixups including:
* many documentation spelling error corrections,
* many formatting consistency corrections,
* moving to semi-qualified replacements for some custom types
* moving to semi-qualified calls for ops:: types
* replacing copy with cloned wherever possible
* reduced unnecessary constraints on specific methods
* improved documentation to explicitly not runtime expections where they may be surprising
* added an iter_with_mutliplicity method for getting (element, count) pairs
* take method returns both element and multiplicity
* explicitly documented an invalid runtime value of `get` that is not machine-enforced
* now consistently using `multiplicity` instead of occasionally using generic letters in some signatures
* modified the test suite to be compatible with future versions of rust
* set minimum tested version to current rust stable:1.47

0.0.3

Adds crate level docs, fixes some links in docs, removes inaccurate "any borrowed form" language until we fix issue #16 and restore that. Also removes some API compat with map that doesn't make sense with an mset. Remove some unnecessary type constraints, and rework remove and remove_times to work with borrowed forms instead of owned forms.

0.0.2

This release includes small updates to documentation and functionality that close out all known issues and api inconsistencies at launch.

0.0.1

Initial release with complete functionality, documentation, and tests. The overall API surface is still uncertain and may not be idiomatic. There are also efficiency improvements yet to be identified.