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, it seems to me that the target information in the input TLSF files is being ignored when going to "low level" output formats like Ltlxba or Acacia. Would it not be better to make sure that the (default) target semantics of the (tool) format respects the intended format of the input file and display some error otherwise?
Alternatively, the writer could also transform the formula as is done in Eval.hs when the overwrite semantics value is set in the configuration.
The text was updated successfully, but these errors were encountered:
Currently, it seems to me that the target information in the input TLSF files is being ignored when going to "low level" output formats like Ltlxba or Acacia. Would it not be better to make sure that the (default) target semantics of the (tool) format respects the intended format of the input file and display some error otherwise?
Alternatively, the writer could also transform the formula as is done in
Eval.hs
when the overwrite semantics value is set in the configuration.The text was updated successfully, but these errors were encountered: