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
After using --debug=tip, we get a tip file where the type instantiations on Return and Proceed are lost, so Inox understands the expression in the tip file as (and this leads to a type error):
Can we add the type instantiations (with _) in Printer.scala? (If so, what term should I use?) Can Inox parse it back?
Yes, you should be able to add the information inside Printer.scala, and you'll need to adapt the parser to handle it as well.
The changes in Printer should take place here. You can use a similar logic to what is used in the case of FunctionInvocation to determine whether to use a qualified identifier (which includes the type annotation).
You'll also need to change the Parserhere to support an optional type ascription.
In a verification condition on the Stainless side, I have a term that contains this:
After using
--debug=tip
, we get a tip file where the type instantiations onReturn
andProceed
are lost, so Inox understands the expression in the tip file as (and this leads to a type error):Can we add the type instantiations (with
_
) inPrinter.scala
? (If so, what term should I use?) Can Inox parse it back?The text was updated successfully, but these errors were encountered: