Gherman
Gherman
> I think it would make sense to add to the release notes information about compatibility between `Ink`, `rustc`, `pallet_contracts`, and `cargo-contract`. WDYT? Good idea. Will do
> > * cargo-contract: `>=4.0.0-rc.3` > > I think cargo-contract: >=4.0.0-rc.3, >=5.0.0 Where does `>=5.0.0` come from? We are also releasing `c-c` 4.0.0 which is backward compat with 4.0.0-rc.3
My personal take. I think this would be a useful feature to have. I personally do not see any security implications with this feature other than a potential user error,...
> It is a limitation that the mutability does not provide us with any guarantees, if a user chooses to use the underlying APIs Indeed, that's why we should discourage...
Please merge master
@FrankBevr is the issue still persisting?
Not a bug but a feature XD
As discussed before, I think we should restrict the direct usage of `ink::env` crate, and encapsulate `Lazy` and `Mapping` storage mutations with a higher-level interface that can infer mutability.
@xermicus what's the status of this issue?
I am not fun of the macro's interface. Wrapping every single call into the macro just to get the syntax highlighting for the `.invoke()` or `.try_invoke()` commands doesn't seem very...