Fix for Useless assignment to local variable#80
Merged
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Contributor
Version Fix for Useless assignment to local variable ReleaseAll Commits
Last updated: 2026-05-12T22:27:32Z |
Contributor
🔄 Submodule Sync Check✅ All submodules are up to date! Automated check · Runs on PR updates |
Contributor
🔍 Release Integrity Verification
|
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
…ariable' Co-authored-by: Copilot Autofix powered by AI <223894421+github-code-quality[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The best fix is to eliminate the unnecessary initial assignment and compute
limitin one step, preserving existing behavior and benchmark intent.In
benchmark/bench-throttle.js, inside the “Policy Evaluation” benchmark callback (around lines 186–193), replace thelet limit = 100; if (...) { ... } else if (...) { ... }block with a singleconst limit = ... ? ... : ...expression. To ensure the computed value is actually used (and avoid further dead-store findings), returnlimitfrom the callback, consistent with other benchmark callbacks that return computed values.No new imports, helper methods, or external dependencies are required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.