This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
Document that Transaction::sign might panic #17026
Merged
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.
Problem
My program panicked, because somewhere in a third-party library, that library called
Transaction::new_signed_with_payer
, which can panic. I’m not sure whether the caller ofTransaction::new_signed_with_payer
was aware of that. Document it, so users can at least be aware of this.Summary of Changes
Add
# Panics
sections. Where possible, include an intra-doc-links to the non-panickingtry_*
variants of these functions.