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
The current behaviour of LTLfParser is to directly translate LTLf formulae into LDLf formulae.
This is not ideal in general, especially for programmatic usage. It conflates two concepts, parsing and translation, into one class. Would be better to have a separate visitor class that does the translation from LTLf to LDLf.
The text was updated successfully, but these errors were encountered:
- fix advanced property tests due to misplaced closed bracket;
- comment out ltlf parsing tests; we now translate to ldlf while parsing ltlf (related to #91)
The current behaviour of
LTLfParser
is to directly translate LTLf formulae into LDLf formulae.This is not ideal in general, especially for programmatic usage. It conflates two concepts, parsing and translation, into one class. Would be better to have a separate visitor class that does the translation from LTLf to LDLf.
The text was updated successfully, but these errors were encountered: