Cosmwasm 0.15

[uint]

Closes #224

[webmaster128]

👍 with this the audit job passes already.

[uint]

Rebased to get rid of the libwasmvm.so update.

[uint]

@webmaster128 I'm struggling with how to represent VoteOption in Go:
https://github.com/CosmWasm/cosmwasm/pull/973/files#diff-ee41fe4124cc812f86177ba54c9fd228f6883afb0750174b704b36faaa31929fR176

I feel like this should be some sort of integer code, and maybe iota would make this easier. But then, we would probably want to hardcode the integer values on Rust side too, wouldn't we? What do you think?

EDIT: Nvm, I think I figured it out.

[webmaster128]

Looks very good

[webmaster128]

I feel like this should be some sort of integer code, and maybe iota would make this easier. But then, we would probably want to hardcode the integer values on Rust side too, wouldn't we? What do you think?

I think the single source of truth is the JSON Schema:

    "VoteOption": {
      "type": "string",
      "enum": [
        "yes",
        "no",
        "abstain",
        "no_with_veto"
      ]
    },

This is what is passed over FFI. Rust does not need to care how Go picks this up. If the int solution of a string solution is better for Go callers, I don't know. I think is is good to fail for non allowed values.

[webmaster128]

🏅