Conversation
…th lock/unlock dependency
|
I think we need to change the behaviour of callv2 before stabilising: #3392 It's out last change but I don't think it will affect the ink! implementation. |
|
bot fmt |
|
@pgherveou https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/5267778 was started for your command Comment |
|
@pgherveou Command |
f7c69ed to
e96f7c5
Compare
|
The CI pipeline was cancelled due to failure one of the required jobs. |
Remove `#[unstable]` on `call_v2`, `instantiate_v2`, `lock_delegate_dependency` and `unlock_delegate_dependency`. See ink! integrations: - call_v2: use-ink/ink#2077 - instantiate_v2: <TODO> - lock/unlock dependency: use-ink/ink#2076
Remove `#[unstable]` on `call_v2`, `instantiate_v2`, `lock_delegate_dependency` and `unlock_delegate_dependency`. See ink! integrations: - call_v2: use-ink/ink#2077 - instantiate_v2: <TODO> - lock/unlock dependency: use-ink/ink#2076
Remove `#[unstable]` on `call_v2`, `instantiate_v2`, `lock_delegate_dependency` and `unlock_delegate_dependency`. See ink! integrations: - call_v2: use-ink/ink#2077 - instantiate_v2: <TODO> - lock/unlock dependency: use-ink/ink#2076
paritytech#3606) Oversight from PR paritytech#3384. These 2 functions should have been tagged as stable
Remove
#[unstable]oncall_v2,instantiate_v2,lock_delegate_dependencyandunlock_delegate_dependency.See ink! integrations:
call_v2cross-contract calls with additional limit parameters use-ink/ink#2077instantiate_v2with additional limit parameters use-ink/ink#2123delegate_dependencyapi calls use-ink/ink#2076