Add bounded PowerShell foreach structure - #98
Merged
Conversation
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
foreachstructural slice into the lockedForEachSyntaxshapeforeachalias behavior and correct statement terminator versus pipeline-chain grammarpwshoracle coverageSafety boundary
This PR intentionally does not publish exact/finite loop binding values or post-loop state. Tasks 7.3-7.7 remain open pending the explicit PowerShell initial-runspace contract and abstract-state analyzer.
Validation
dotnet build -c Release --no-restore(0 warnings)dotnet test -c Release --no-build --no-restore(1,739 passed)dotnet format --verify-no-changes --no-restorepwsh ./scripts/Add-FileHeaders.ps1 -Verifyopenspec validate v0-3-structured-shell-analysis --strictAdversarial review
GO for exact staged fingerprint
4948791292e7b7661b1a2061a5bac02a1af2b7649ab41bf512f5a5382cdca232after three earlier NO-GO snapshots exposed and fixed command-resolution mutation, quoted/provider-qualified path, continuation completeness, and statement-boundary bugs.