Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

additional doc on repatriate_reserved #8135

Closed
wants to merge 1 commit into from

Conversation

gui1117
Copy link
Contributor

@gui1117 gui1117 commented Feb 16, 2021

Related paritytech/polkadot-sdk#337

repatriate_reserved is failing if beneficiary is not an existing account, thus better to make it explicit in the doc.

Otherwise we can also make repatriate_reserved allowing to repatriate to unexisting account but this is changing the current logic.

@gui1117 gui1117 added A0-please_review Pull request needs code review. A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. labels Feb 16, 2021
@liuchengxu
Copy link
Contributor

Making it even more explicit is good, but the problem of paritytech/polkadot-sdk#337 still persists, awaiting more inputs.

/// `beneficiary`. `beneficiary` must exist for this to succeed. If it does not, `Err` will be

@gui1117
Copy link
Contributor Author

gui1117 commented Feb 16, 2021

I missunderstood the original issue, so I close it

@gui1117 gui1117 closed this Feb 16, 2021
@gui1117 gui1117 deleted the gui-precise-doc-repatriate_reserved branch February 16, 2021 18:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-please_review Pull request needs code review. A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants