diff options
| author |  Jason Gross <jgross@mit.edu> | 2019-01-17 15:59:04 -0500 |
|---|---|---|
| committer |  Jason Gross <jasongross9@gmail.com> | 2019-01-18 16:38:13 -0500 |
| commit | 70bdfbd3804d61535e280cecc042f73729664df4 (patch) | |
| tree | 2eb07bb551ccc976b931fd51e784c63bf239d58c /src/Util | |
| parent | 6b762468c54fd8084dda854c968684c903bea54c (diff) | |
Be stricter about rejecting command line arguments
We no longer accept `1,1` as a valid bitwidth.
This closes #488. It does not quite fix the issue as stated, but it
resolves the underlying confusion that generated it (the difference
between passing `1,1` as a `c` vs passing `1,1` as a bitwidth). It
still might be nice to someday emit warnings as suggested in the bug
report.
I've also factored out a bit of code to make it easier to report parse
failures, by folding over a list of parses.
Diffstat (limited to 'src/Util')
0 files changed, 0 insertions, 0 deletions