You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Telamon-gen generates a backtrace when it encounters a user error. This makes it hard to use. It should report errors with line and column numbers instead.
Remaining actions:
Separate declaration and definition
Sets type checking and declaration
Generic choices type checking
Enum type checking and declaration
Integer type checking and declaration
NumericSet type checking and declaration
Counter type checking and declaration
Constraint type checking and declaration
Trigger type checking and declaration
Quotient sets type checking and delclaration
The text was updated successfully, but these errors were encountered:
* Lexer captures InvalidToken and parser returns it as a
* Positions can now be implemented by @l and @r tokens at Lalrpop #5 .
* The F/lex FFI part of lexer is now more documented.
* The token position is now checked and implemented from the Lexer grammar.
Here are my comments on the current error checking:
many function could be factorized between IntegerDef, EnumDef and CounterDef. All three statements define a new choice so it makes sense. Moreover, the names of IntegerDef must not collide with the names of EnumDef and CounterDef.
Choice parameters should only be checked once sets are defined. Indeed the set may be defined after the enum in the input file.
the name parametric is used where it should be parameter
87: Spanned name for Var Definition r=adjivas a=adjivas
Short PR to prepare EnumDef check cases of issue #5 .
Co-authored-by: adjivas <[email protected]>
borsbot
added a commit
that referenced
this issue
Aug 2, 2018
89: Enumeration check r=adjivas a=adjivas
Check case for #5 .
* [x] undefined_field_antisymmetric: A antisymmetric should refers a defined fields from same enum.
Co-authored-by: adjivas <[email protected]>
Currently, Telamon-gen generates a backtrace when it encounters a user error. This makes it hard to use. It should report errors with line and column numbers instead.
Remaining actions:
The text was updated successfully, but these errors were encountered: