-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Impossible" errors #789
Comments
err:XS010, a pipeline contains a step whose specified inputs, outputs, and options do not match the for steps of that type We have more specific error codes for each of those conditions. |
err:XS0027, It is a static error if an option is specified with both the shortcut form and the long form. I guess this one isn't impossible, but I think it's subsumed by My implementation transforms shortcut options into "regular" options, so I always get |
|
err:XS0048, It is a static error to use a declared step (an extension step without a body) as a compound step I throw XS0100 because I know what all the compound steps are and I reject the attempt to construct the invalid compound step long before I look at whether or not the wrapper is declared as an atomic, extension step. |
I'm using this issue to track errors that are in the specification(s) but are unlikely to be raised. I'm not sure we need to do anything about them, but the test suite reports how many tests we have for error conditions. If an error is never raised, then that's a little misleading with respect to coverage...
The text was updated successfully, but these errors were encountered: