CHC: A number of fixes for command line arguments handling #192
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.
With these changes we no longer have a ton of open POs when programs
use command line arguments.
These fixes both issues when accessing
argv[0]directly (which is givenspecial treatment) and accessing other command line arguments after
checking that those exist (by looking at the value of
argc).Before these changes, these were all the open POs for a simple hello world
program:
Two pending things which I will tackle on the next set of commits:
close:
argcbefore accessingargvthen the diagnostics all relate to the fact that we don't haveinvariants to verify whether the access is correct or not, which makes it
sound like there's a bug in CHC. For example: