Introduction to the novelty of substrat source code: indexing of call calls and fully completing the materialization of storage layer

20220523 - 20220529

Add a script to run all Benchmarks The order of

4 Since the month , 

Benchmark

The related commands and subcommands are updated and extended ,  This week, a new script was added to execute all

Benchmark

command ;  Also on Benchmark The relevant source code has been revised and updated .  Script file based on https://github.com/paritytech/polkadot/blob/master/scripts/ci/run_benches_for_runtime.sh.

details :https://github.com/paritytech/substrate/pull/11493

newly added Call Indexed attribute macro

For the moment ,  whatever dispatchable Of Call No execution order is set ,  Its execution is roughly determined according to the trading pool and weight rules ,  Now provide a

#[pallet::call_index($idx)]

Attribute macro ,  For fixing

Call

enum Variable position index value in ,  No execution sequence is involved ,  It is only used for reference to facilitate distinguishing and other scenarios .

details : https://github.com/paritytech/substrate/pull/11381

Transactional, comprehensive updates to the storage tier and bug Repair

since 2021 From the year onwards , Parity The core developer of Shawn Tabrizi Submit a new idea for storage layer transaction processing ,  Basically divided into 3 Walking :  The first step is to set a limit constant for the number of nested transaction layers ,  The second step is at all Frame and Pallet For transactional Call Call to implement a new transaction processing mechanism ,  The third step is to

Transaction

renamed ,  So that " Business " Follow " transaction " Distinguish between the two ( Both words are

Transaction

).

This year, 4 The first step of the month has been completed ,  The most critical second step was not fully realized until this week .  This section provides some new auxiliary functions

with_storage_layer

, 

in_storage_layer

etc. ,  To replace the former

with_transactional

function ,  Compared with the previous way ,  The return value of the new function is a

Result

,  This is more consistent

Business

Definition of processing :  Return to success ,  Or fail to rollback .

The new update to the storage layer also includes a

DispatchWithStorageLayer

Of trait Interface ,  whatever pallet Can call one of the

.dispatch_with_storage_layer

Method to use the new storage layer transaction logic ,  meanwhile

UnfliteredDispatchable

For compatibility with previous processing logic .

in addition ,  The third step may not be completed ,  Because the changes are too big ,  It is not very compatible with the previous code .

details : https://github.com/paritytech/substrate/pull/11431

About storage layer updates ,  There will be more this week Gavin It is easy to delete the same for multiple stores key The problem of .

details : https://github.com/paritytech/substrate/pull/11490

This paper is about SEP Creation  Original group articles ,  By pengyalun

Unauthorized ,  Do not reprint .