fix(linter): align S001 indirect expansion parity#596
Merged
Conversation
Contributor
Macro CLI Benchmark DeltasCompared Positive deltas mean slower
Aggregate
Flagged aggregate regressions over +5.0%: 0 Per-fixture macro deltas
Largest changesRegressions
Improvements
Non-zero benchmark exit codes
|
d99006e to
667724b
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d99006e7b4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
This was referenced Apr 25, 2026
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
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.
Summary
name=target; echo ${!name}are now treated as safe for S001, while dynamic names such asname=$1; echo ${!name}still report.crates/shuck-cli/tests/testdata/corpus-metadata/s001.yaml.docs/S001_BUGS.mdto classify the current reviewed S001 divergence buckets and track the remaining work, including the rule that fixed records must also be removed from S001 corpus metadata.Root Cause
S001 was checking whether the resolved indirect target value was safe. Black-box ShellCheck probes show SC2086 instead suppresses based on whether the visible indirection carrier is field-safe.
Remaining Arithmetic/Operator Notes
The remaining two records in the arithmetic/operator bucket are still open and remain in metadata. Follow-up probing showed they are separate shapes:
meshrdf_generate_table.sh:3374: likely needs a narrow field-safe rule for assignments whose whole RHS is an arithmetic expansion, not any value that merely contains arithmetic.dehydrated:1077: likely depends on helper/call-order value knowledge for safe literal assignments before substring expansion, not a broad substring suppression.Validation
cargo test -p shuck-linter indirect_ -- --nocapturecargo test -p shuck-linter unquoted_expansioncargo fmt --checkmake large-corpus-report SHUCK_LARGE_CORPUS_RULES=S001The targeted corpus report remains structurally clean with
implementation_diffs=0andmapping_issues=0; reviewed divergences dropped from 72 to 70.