FuelLabs/sway - CodSpeed

FuelLabs

sway

Blog Docs Changelog

Performance History

Latest Results

rebase issues

xunilrj/trivial-checks

7 hours ago

Add `dynamic_storage` experimental feature and offset to `srw` opcode (#7565) ## Description This PR is the first step in implementing #7560. The PR: - bumps `fuel-vm` dependencies to v0.66. - bumps `fuel-core` dependencies to v0.48. - bumps `fuels-rs` dependencies to v0.77. - adds the `dynamic_storage` experimental feature. - extends the `srw` opcode with an immediate offset. - extends the `__state_load_word` intrinsic with the offset. - extends the `state_load_word` IR operation with the offset. - updates `gas_costs_values.json` to use the latest `V7` gas costs defined in `fuel-core` repository [`chainspec/local-testnet/chain_config.json`](https://github.com/FuelLabs/fuel-core/blob/addb4c0e97615b1476fe79bf63672b4127209a8e/bin/fuel-core/chainspec/local-testnet/chain_config.json) Additionally, the PR: - Fixes #7564 by adding a dedicated `CompileError::IntrinsicArgNotConstant`. ## Breaking changes Defining opcodes via the `define_op_codes` macros does not allow for customization based on feature flags. Also, opcodes are modeled as enums in code generation. Changing the whole mechanics of opcode definition just to support two different `srw` opcodes does not pay off, especially because we do not expect `srw` to be used in real-life code. Thus, **supporting only `srw res is_set slot imm6` will be a breaking change not hidden behind a feature flag**. ## Checklist - [x] I have linked to any relevant issues. - [x] I have commented my code, particularly in hard-to-understand areas. - [ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book). - [ ] If my change requires substantial documentation changes, I have [requested support from the DevRel team](https://github.com/FuelLabs/devrel-requests/issues/new/choose) - [x] I have added tests that prove my fix is effective or that my feature works. - [x] I have added (or requested a maintainer to add) the necessary `Breaking*` or `New Feature` labels where relevant. - [x] I have done my best to ensure that my PR adheres to [the Fuel Labs Code Review Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md). - [x] I have requested a review from the relevant team or maintainers.

master

9 hours ago

Remove unused `poke` function from `storage_instructions` test

ironcev/dynamic-storage-srw

16 hours ago

Bump `fuel-core` to v0.48 in SDK harness tests

ironcev/dynamic-storage-srw

17 hours ago

Add comprehensive benchmarks for `StorageVec` (#7588) ## Description This PR is a continuation of #7583. It adds additional benchmarks for benchmarking all `StorageVec` API methods for different element sizes and different number of elements stored. The `README.md` explains the benchmarks and how to use the benchmarking infrastructure. The `RESULTS.md` contains the benchmarking results for the current `storage` implementation. ## Checklist - [x] I have linked to any relevant issues. - [x] I have commented my code, particularly in hard-to-understand areas. - [ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book). - [ ] If my change requires substantial documentation changes, I have [requested support from the DevRel team](https://github.com/FuelLabs/devrel-requests/issues/new/choose) - [ ] I have added tests that prove my fix is effective or that my feature works. - [ ] I have added (or requested a maintainer to add) the necessary `Breaking*` or `New Feature` labels where relevant. - [x] I have done my best to ensure that my PR adheres to [the Fuel Labs Code Review Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md). - [x] I have requested a review from the relevant team or maintainers.

master

21 hours ago

Update Cargo.lock

ironcev/dynamic-storage-srw

2 days ago

Merge branch 'master' into ironcev/dynamic-storage-srw

ironcev/dynamic-storage-srw

2 days ago

Pin tracing-subscriber to 0.3.19 (#7587) ## Summary Pin `tracing-subscriber` to `0.3.19`. ## Why `forc` output regressed because newer `tracing-subscriber` releases escape ANSI sequences in normal terminal output. This was not a snapshot-test-only issue; it changed compiler and CLI output behavior in general. Pinning to `0.3.19` restores the previous behavior until we choose a different fix. See the upstream `0.3.20` release notes: https://github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.20 ## Validation - `cargo check -p forc -p forc-util`

master

2 days ago

Latest Branches

-1%

Attribute for checking of trivial encoding and decoding#7575

8 hours ago

a9cf665

xunilrj/trivial-checks

Add `dynamic_storage` experimental feature and offset to `srw` opcode#7565

17 hours ago

e3c9bf0

ironcev/dynamic-storage-srw

-11%

Support attributes and constants in self `impl Contract`s#7580

18 days ago

a62000f

ironcev/fix-self-impl-contract

Home Terms Privacy Docs