Register error-chain cfg for rustc checking. - #241
Merged
Conversation
philippem
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Register
has_error_description_deprecatedas a known Rust cfg.error-chain 0.12.4emits this cfg while expanding its macro in electrs. Recent Rust toolchains therefore report it as unexpected, even though it originates inthe dependency.
This narrowly registers that cfg instead of disabling the
unexpected_cfgslint. There are no runtime behavior changes.Testing
cargo check --lockedcargo check --features liquid --lockedBoth builds pass and no longer emit the
has_error_description_deprecatedwarning.