Type Scalc flow to avoid unresolved typing

With the new EAppOp node, the typing of operator application has changed and this causes some problems
with the example in test_scope/good/nothing.catala_en when retyping the LCalc to go to Scalc. This
commit changes the weird thing that for generating Scalc, the "typed" parameter was set to "untyped".
This commit is contained in:
Denis Merigoux 2024-01-17 13:08:20 +01:00
parent a1ab58478c
commit ca8e4989ea
No known key found for this signature in database
GPG Key ID: EE99DCFA365C3EE3

View File

@ -295,7 +295,7 @@ module Passes = struct
~monomorphize_types :
Scalc.Ast.program * Scopelang.Dependency.TVertex.t list =
let prg, type_ordering =
lcalc options ~includes ~optimize ~check_invariants ~typed:Expr.untyped
lcalc options ~includes ~optimize ~check_invariants ~typed:Expr.typed
~avoid_exceptions ~closure_conversion ~monomorphize_types
in
Message.emit_debug "Retyping lambda calculus...";