6555143478
Is there any advantage trying to lay out the re-exports to give users an idea of the crate structure? We have the explicit aim that users who depend on `bitcoin` do not ever need to reach directly into `primitives` (or `units`) however it is kind of nice to know where things come from, saves jumping to multiple files looking for them (for those of us that jump to files manually). I do not know how all the re-exports interact with other folks IDEs, I personally open files manually and just remember where stuff is. |
||
|---|---|---|
| .. | ||
| contrib | ||
| src | ||
| CHANGELOG.md | ||
| Cargo.toml | ||
| README.md | ||
README.md
Rust Bitcoin - primitive types.
This crate provides primitive data types that are used throughout the
rust-bitcoin ecosystem.
Semver compliance
Functions marked as unstable (e.g. foo__unstable) are not guaranteed to uphold semver compliance.
They are primarily provided to support rust-bitcoin.
Minimum Supported Rust Version (MSRV)
This library should always compile with any combination of features on Rust 1.63.0.
Licensing
The code in this project is licensed under the Creative Commons CC0 1.0 Universal license. We use the SPDX license list and SPDX IDs.