Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Granularity of static errors #333
From a discussion with @ndw
As a general rule we might say, that we want an error code for this generic error which is raised every time a pipeline violates the RNC-grammar. It is then up to the implementation to provide some useful hint what went wrong. For non-grammar errors (e.g. double port names) we will still need specific error codes.
As a result of this strategy we could reduce the number of static errors and make the specs more editable because we would not have a grammar expression AND a code anymore.