Sample
ArgParser.parse greedily consumes subsequent flag tokens as literal option values when a single option expecting a value is followed by a hyphenated argument
sha256:bb553cdbba6515874c02f0505de8bf76311a0d6eb43308f02fb9568806121c59
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- ArgParser.parse greedily consumes subsequent flag tokens as literal option values when a single option expecting a value is followed by a hyphenated argument HOW
- Packages
- args 2.6.0
- Environment
- dart
- Created
- 2026-08-17T02:03:39Z
Commonly assumed
When an option expecting a value is immediately followed by a registered flag like --verbose, ArgParser.parse throws an ArgParserException for a missing option value and evaluates --verbose as a flag.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- ArgParser.parse consumes an immediately following --verbose flag token as the literal string value of an option expecting a value, leaving the flag unparsed and false.
- assert(results['output'] == '--verbose');
- assert(results['verbose'] == false);
- assert(results.wasParsed('verbose') == false);
Files
- NOTES.md
- csx.json
- pubspec.lock
- pubspec.yaml
- test/contract.dart
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- dart 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · pub@1 · 2026-08-17 · ed25519:d91480838ac982c9