Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix some outdated links and descriptions #13

Merged
merged 1 commit into from Mar 1, 2017

Conversation

michaelsproul
Copy link
Contributor

This commit updates the doc link to https://docs.rs/multihash, which will auto-update when new a new version is published to crates.io. Currently, the docs hosted on Github pages are out of date.

I also added a doc link to Cargo.toml so a documentation link shows up on crates.io.

Finally, I updated the README section and the doc comments about supported hash functions so they represent the current state of the code.

@dignifiedquire dignifiedquire merged commit 4de57be into multiformats:master Mar 1, 2017
@dignifiedquire
Copy link
Member

Thank you :octocat:

@michaelsproul michaelsproul deleted the docs branch March 1, 2017 09:36
vmx added a commit that referenced this pull request Sep 30, 2020
Instead of deriving a Multihash enum, derive from a Code enum.

This commit also combines the previously generated `Multihash` enum with
the `RawMultihash` struct. There is now a single `Multihash` type which
is generic over its digest size.

The derived `Code` enum is used for hashing, the `Multihash` only contains
static, general data.

Closes #12, #13.
vmx pushed a commit that referenced this pull request Sep 30, 2020
* feat: derive from Code enum

Instead of deriving a Multihash enum, derive from a Code enum.

This commit also combines the previously generated `Multihash` enum with
the `RawMultihash` struct. There is now a single `Multihash` type which
is generic over its digest size.

The derived `Code` enum is used for hashing, the `Multihash` only contains
static, general data.

Closes #12, #13.

* fix: don't clone the digest

* feat: introduce `max_size` attribute

The digests are stack allocated. We cannot determine the biggest digest size
that is used at compile time, hence you need to specify the maximum allocated
size your custom code table should use via `[#mh(max_size = …)]` on the enum
you derive the table from.

* fix: enable the arb module again

* fix: properly use local versions of imports

This way you only need to import the derive and not also additional
(seemingly unrelated) types.

* fix: make Serde support work again

* fix: make Parity Scale Codec support work again

* feat: create MultihashCode trait

Instead of just implementing it on the code enum, use a trait instead.
This way other libraries can create digests without knowing the concrete
type.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants