rust-bitcoin

bitcoin: Move witness_program module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from witness_program module into error submodule
and re-export.

bitcoin: Move block module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from block module into error submodule and re-export.

bitcoin: Move bip158 module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from bip158 module into error submodule and re-export.

bitcoin: Move script module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from script module into error submodule and re-export.

bitcoin: Move bip32 module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from bip32 module into error submodule and re-export.

bitcoin: Move sign_message module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from sign_message module into error submodule and
re-export.

Make consensus errors pub and no_inline

As part of the process of moving errors to error submodules, all error
types at the top-level should be no_inline. Further, we want all errors
in top-level modules to be re-exported from a pub error submodule.

Make consensus::error pub and change error re-exports to be no_inline.

bitcoin: Move network module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from network module into error submodule and re-export.

bitcoin: Move consensus_validation module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from consensus_validation module into error submodule
and re-export.

bitcoin: Move taproot module errors to error submodule

At present, some modules in bitcoin separate error types into
submodules with re-exports while others simply define the error types
in the module. This inconsistency is confusing and makes the docs vary.
All error types for each top-level module should be moved into a
relevant submodule and re-exported without inline docs.

Move error types from taproot module into error submodule and re-export.

Make address module errors no_inline

As part of the process of moving errors to error submodules, all error
types at the top-level should be no_inline.

consensus_encoding: Bump version to 0.2.0

This release is a release candidate for `consensus_encoding v1.0.0`.
And hopefully it is the last one. `v1.0.0` release imminent ...

In preparation for release add a changelog entry, bump the version,
and update the lock files.

chacha20_poly1305: bump minor version and changelog for v0.2.0

fuzz: pin cargo-fuzz to 0.12.0

p2p: Fix types and wording for decoder errors

Some of the decoder errors in p2p include types in the doc comments.
For some of these, the choice of a/an is incorrect, and for others, the
decoder error type itself is mentioned, instead of the decoder result
type.

Adjust wording and types for AddressDecoderError,
V1MessageHeaderDecoderError, PingDecoderError, and PongDecoderError.

primitives: Replace decoder definitions with decoder_newtype macro

Introduce decoder_newtype macro in primitives through the include!
macro.
Replace all newtype Decoder structs in primitives with decoder_newtype
calls.

units: Replace decoder definitions with decoder_newtype macro

Throughout the crates, there exist various decoder types that are
newtype wrappers around existing encoders. Almost all of these use the
same boilerplate for most of their logic and can be replaced by a
macro that provides the same functionality.

Introduce private decoder_newtype macro in include file and introduce
to units crate through include! macro.
Replace all Decoder structs in units with decoder_newtype calls.

Update API files

As part of introducing explicit impls for std::error::Error, various
error types are now recorded as including a source() impl. To satisfy
the API checker, the files must be updated.

Update API files with just check-api

base58: Add explicit None return impl for std::error::Error

The std::error::Error impls on many error types rely on the default
implementation for the trait, which returns None. While these are
correct, explicit return values make the functionality more obvious to
later developers without requiring pre-existing knowledge of the trait
or needing to search documentation.

Replace all default impls of std::error::Error with explicit impls
returning None.

p2p: Add explicit None return impl for std::error::Error

The std::error::Error impls on many error types rely on the default
implementation for the trait, which returns None. While these are
correct, explicit return values make the functionality more obvious to
later developers without requiring pre-existing knowledge of the trait
or needing to search documentation.

Replace all default impls of std::error::Error with explicit impls
returning None. For enum errors, also return None for each match arm.

bitcoin: Add explicit None return impl for std::error::Error

The std::error::Error impls on many error types rely on the default
implementation for the trait, which returns None. While these are
correct, explicit return values make the functionality more obvious to
later developers without requiring pre-existing knowledge of the trait
or needing to search documentation.

Replace all default impls of std::error::Error with explicit impls
returning None. For enum errors, also return None for each match arm.

hashes: Add explicit None return impl for std::error::Error

The std::error::Error impls on many error types rely on the default
implementation for the trait, which returns None. While these are
correct, explicit return values make the functionality more obvious to
later developers without requiring pre-existing knowledge of the trait
or needing to search documentation.

Replace all default impls of std::error::Error with explicit impls
returning None.

consensus_encoding: Add explicit None return impl for std::error::Error

The std::error::Error impls on many error types rely on the default
implementation for the trait, which returns None. While these are
correct, explicit return values make the functionality more obvious to
later developers without requiring pre-existing knowledge of the trait
or needing to search documentation.

Replace all default impls of std::error::Error with explicit impls
returning None.

primitives: Add explicit None return impl for std::error::Error

The std::error::Error impls on many error types rely on the default
implementation for the trait, which returns None. While these are
correct, explicit return values make the functionality more obvious to
later developers without requiring pre-existing knowledge of the trait
or needing to search documentation.

Replace all default impls of std::error::Error with explicit impls
returning None. For enum errors, also return None for each match arm.

units: Add explicit None return impl for std::error::Error

The std::error::Error impls on many error types rely on the default
implementation for the trait, which returns None. While these are
correct, explicit return values make the functionality more obvious to
later developers without requiring pre-existing knowledge of the trait
or needing to search documentation.

Replace all default impls of std::error::Error with explicit impls
returning None.