New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Describe the effect of ink! messages returning a `Result::Err` #39

Open

cmichi opened this issue Nov 25, 2021 · 1 comment

Labels

Collaborator

cmichi commented Nov 25, 2021 •

edited

Loading

See the release notes of ink! rc7 for more details: https://github.com/paritytech/ink/blob/cmichi-release-ink-rc7/RELEASES.md.

We should highlight how the behavior is for sub-contracts.

Maybe @Robbepop wants to tackle this?

cmichi added the documentation label

Contributor

SkymanOne commented Mar 15, 2023

Should be addressed in https://use.ink/basics/cross-contract-calling with the mentioned of LangErr introduced in https://github.com/paritytech/ink/blob/master/CHANGELOG.md#constructors-and-messages-now-return-langerrors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment