Skip to content
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

Remove non_exhaustive from IBC message types. #1449

Merged
merged 2 commits into from
Oct 14, 2022
Merged

Remove non_exhaustive from IBC message types. #1449

merged 2 commits into from
Oct 14, 2022

Commits on Oct 13, 2022

  1. Remove non_exhaustive from IBC message types. 

    IBC message types being non exhaustive means that contract authors
have to include a wildcard arm in any match expression deailing with
them. IMO, this is actually quite undesirable. I my contract to fail
to compile if a message is added!
    @0xekez
    0xekez committed Oct 13, 2022
    Configuration menu
    Copy the full SHA
    b48a17c View commit details
    Browse the repository at this point in the history

Commits on Oct 14, 2022

  1. Elaborate on CHANGELOG entry

    @webmaster128
    webmaster128 committed Oct 14, 2022
    Configuration menu
    Copy the full SHA
    41135a8 View commit details
    Browse the repository at this point in the history