Skip to content
Snippets Groups Projects
Select Git revision
  • gh-readonly-queue/master/pr-8070-f1d1d9c5c8d0effe4c60b81f6eaaa112ddc14658 protected
  • 8070
  • gh-readonly-queue/master/pr-8062-342f46a4e37749a749a405e6cacece9687f2a9f2 protected
  • master default protected
  • gh-readonly-queue/master/pr-7703-d13f1f60adc942621e2d335b0ea5d54accc02140 protected
  • gh-readonly-queue/master/pr-8071-9be43c0abf0a02a28d8fd4bbe9cfaed17dfcf18c protected
  • 8083
  • 6224
  • 8068
  • 8091
  • gh-readonly-queue/master/pr-8057-82827221b774e24b98cd7f2306c1f2c1ea281c40 protected
  • 8020
  • 6515
  • 8089
  • 6523
  • 6630
  • 8088
  • 6532
  • gh-readonly-queue/master/pr-8020-82827221b774e24b98cd7f2306c1f2c1ea281c40 protected
  • 8053
20 results
Compare History
PG Herveou's avatar
Update benchmarking macros (#3934)
PG Herveou authored 
Current benchmarking macro returns a closure with the captured
benchmarked code.
This can cause issues when the benchmarked code has complex lifetime
requirements.

This PR updates the existing macro by injecting the recording parameter
and invoking the start / stop method around the benchmarked block
instead of returning a closure

One other added benefit is that you can write this kind of code now as
well:

```rust
let v;
#[block]
{ v = func.call(); }
dbg!(v); // or assert something on v
```


[Weights compare
link](https://weights.tasty.limo/compare?unit=weight&ignore_errors=true&threshold=10&method=asymptotic&repo=polkadot-sdk&old=pg/fix-weights&new=pg/bench_update&path_pattern=substrate/frame/**/src/weights.rs,polkadot/runtime/*/src/weights/**/*.rs,polkadot/bridges/modules/*/src/weights.rs,cumulus/**/weights/*.rs,cumulus/**/weights/xcm/*.rs,cumulus/**/src/weights.rs)

---------

Co-authored-by: command-bot <>
Co-authored-by: default avatarOliver Tale-Yazdi <oliver.tale-yazdi@pari...>
d38f6e67
Name Last commit Last update
..
.config
.maintain
bin
client
deprecated/hashing
docker
docs
frame
primitives
scripts
test-utils
utils
zombienet
.dockerignore
.editorconfig
.git-blame-ignore-revs
.gitattributes
HEADER-APACHE2
HEADER-GPL3
LICENSE-APACHE2
LICENSE-GPL3
README.md
README.md

Substrate

GitHub license GitLab Status PRs Welcome Stack Exchange

Substrate is a next-generation framework for blockchain innovation 🚀.

Getting Started

Head to docs.substrate.io and follow the installation instructions. Then try out one of the tutorials. Refer to the Docker instructions to quickly run Substrate, Substrate Node Template, Subkey, or to build a chain spec.

Community & Support

Join the highly active and supportive community on the Substrate Stack Exchange to ask questions about use and problems you run into using this software. Please do report bugs and issues here for anything you suspect requires action in the source.

Contributions & Code of Conduct

Please follow the contributions guidelines as outlined in docs/contributor/CONTRIBUTING.md. In all communications and contributions, this project follows the Contributor Covenant Code of Conduct.

Security

The security policy and procedures can be found in docs/contributor/SECURITY.md.

License

The reason for the split-licensing is to ensure that for the vast majority of teams using Substrate to create feature-chains, then all changes can be made entirely in Apache2-licensed code, allowing teams full freedom over what and how they release and giving licensing clarity to commercial teams.

In the interests of the community, we require any deeper improvements made to Substrate's core logic (e.g. Substrate's internal consensus, crypto or database code) to be contributed back so everyone can benefit.