ligo/src/passes/02-concrete_to_imperative/pascaligo.mli

(** Converts PascaLIGO programs to the Simplified Abstract Syntax Tree. *)

open Trace
open Ast_imperative

module Raw = Parser.Pascaligo.AST
module SMap = Map.String

(** Convert a concrete PascaLIGO expression AST to the imperative
    expression AST used by the compiler. *)
val compile_expression : Raw.expr -> (expr , Errors_pascaligo.abs_error) result

(** Convert a concrete PascaLIGO program AST to the miperative program
    AST used by the compiler. *)
val compile_program : Raw.ast -> (program, Errors_pascaligo.abs_error) result
Delete dead code and add .mli docs to simplify/pascaligo.ml 2019-10-03 15:32:16 -07:00			`(** Converts PascaLIGO programs to the Simplified Abstract Syntax Tree. *)`

Interface for Ocaml code 2019-10-07 14:18:32 +00:00			`open Trace`
compiling 2020-03-12 23:20:39 +01:00			`open Ast_imperative`
Delete dead code and add .mli docs to simplify/pascaligo.ml 2019-10-03 15:32:16 -07:00
			`module Raw = Parser.Pascaligo.AST`
			`module SMap = Map.String`

rename AST to imperative, sugar and core. Factor code in compile 2020-03-16 14:28:05 +01:00			`(** Convert a concrete PascaLIGO expression AST to the imperative`
Refactoring of the AST and simplfier of PascaLIGO. Some weeks ago, anonymous functions as expressions were added to PascaLIGO, unfortunately in a manner that allowed in theory for contexts in which a named function was found when an anonymous was expected, and vice-versa. That explains that the simplifier had two new possible errors: * unexpected_anonymous_function ("you provided a function declaration without name") * unexpected_named_function I changed the AST and the parser so that function expressions correspond to anonymous functions (without block) and function declarations correspond to named functions. I also removed a error in the simplifier, which was unused: * bad_bytes ("you provided a function expression with a name (remove it)") 2020-01-09 17:26:07 +01:00			`expression AST used by the compiler. *)`
result monad refactoring: - do not use plain JSON rep for errors and use polymorphic variants instead - split formatting for human readable and JSON output - no more simple_errors simple_fails - much less result bindings used in stages 2020-06-12 13:33:14 +02:00			`val compile_expression : Raw.expr -> (expr , Errors_pascaligo.abs_error) result`
Delete dead code and add .mli docs to simplify/pascaligo.ml 2019-10-03 15:32:16 -07:00
rename AST to imperative, sugar and core. Factor code in compile 2020-03-16 14:28:05 +01:00			`(** Convert a concrete PascaLIGO program AST to the miperative program`
Refactoring of the AST and simplfier of PascaLIGO. Some weeks ago, anonymous functions as expressions were added to PascaLIGO, unfortunately in a manner that allowed in theory for contexts in which a named function was found when an anonymous was expected, and vice-versa. That explains that the simplifier had two new possible errors: * unexpected_anonymous_function ("you provided a function declaration without name") * unexpected_named_function I changed the AST and the parser so that function expressions correspond to anonymous functions (without block) and function declarations correspond to named functions. I also removed a error in the simplifier, which was unused: * bad_bytes ("you provided a function expression with a name (remove it)") 2020-01-09 17:26:07 +01:00			`AST used by the compiler. *)`
result monad refactoring: - do not use plain JSON rep for errors and use polymorphic variants instead - split formatting for human readable and JSON output - no more simple_errors simple_fails - much less result bindings used in stages 2020-06-12 13:33:14 +02:00			`val compile_program : Raw.ast -> (program, Errors_pascaligo.abs_error) result`