David Semakula comments

Results 16 comments of


                                            David Semakula

Errors when using "cargo-contract" v 5.0.3.

@CasiniNift @realtakahashi Thanks for reporting. This is likely caused by "unsafe" `usize` to `u8` conversions originating from code generated by the derived implementations of the SCALE `Encode` and `Decode` traits....

Errors when using "cargo-contract" v 5.0.3.

@CasiniNift be sure to run `cargo clean` before running `cargo contract build` after installing `v5.0.2` If that sill fails for some reason, you can try adding `#[allow(clippy::cast_possible_truncation)]` just above [this...

Errors when using "cargo-contract" v 5.0.3.

Closing as root cause was solved upstream in `parity-scale-code`, see links below for details - https://github.com/paritytech/parity-scale-codec/issues/713 - https://github.com/paritytech/parity-scale-codec/pull/715

Add compile-time check that prevents ink! messages with a `&self` receiver from mutating state via `ink_env`

@cmichi We already gave up on landing this in v6 due to resource constraints, I just forgot to update its tags on the board. So marking it optional is fine.

Unable to deploy Ink smart contract to the local node.

Alright, looking into this

Discussion: `Balance` vs `U256`, should we expose only a singular balance type to users?

After a bit more thought, I also think that unifying around `U256` makes the most sense from a "core language" perspective. The rationale on my side is that for the...