val create_sign : Common.Path.t -> Sign.t

create_sign path creates a signature with path path with ghost modules as dependencies.

type sig_state = {
signature : Sign.t;(*

Current signature.

in_scope : Term.sym Lplib.Extra.StrMap.t;(*

Symbols in scope.

alias_path : Common.Path.t Lplib.Extra.StrMap.t;(*

Alias to path map.

path_alias : string Common.Path.Map.t;(*

Path to alias map.

builtins : Term.sym Lplib.Extra.StrMap.t;(*


notations : Sign.notation Term.SymMap.t;(*


open_paths : Common.Path.Set.t;(*

Open modules.


State of the signature, including aliasing and accessible symbols.

type t = sig_state
val dummy : sig_state

Dummy sig_state.

val add_symbol : sig_state -> Term.expo -> Term.prop -> Term.match_strat -> bool -> Common.Pos.strloc -> Term.term -> bool list -> Term.term option -> sig_state * Term.sym

add_symbol ss expo prop mstrat opaq id typ impl def generates a new signature state from ss by creating a new symbol with expo e, property p, strategy st, name x, type a, implicit arguments impl and optional definition def. This new symbol is returned too.

val add_notation : sig_state -> Term.sym -> Sign.notation -> sig_state

add_notation ss s n maps s notation to n in ss.

val add_builtin : sig_state -> string -> Term.sym -> sig_state

add_builtin ss n s generates a new signature state from ss by mapping the builtin n to s.

add_notations_from_builtins notmap bm add notations for symbols mapped to the builtins "0" and "+1".

val open_sign : sig_state -> Sign.t -> sig_state

open_sign ss sign extends the signature state ss with every symbol of the signature sign. This has the effect of putting these symbols in the scope when (possibly masking symbols with the same name). Builtins and notations are also handled in a similar way.

val of_sign : Sign.t -> sig_state

of_sign sign creates a state from the signature sign and open it as well as the ghost signatures.

val find_sym : prt:bool -> prv:bool -> sig_state -> Term.qident Common.Pos.loc -> Term.sym

find_sym ~prt ~prv b st qid returns the symbol corresponding to the qualified identifier qid. If fst qid.elt is empty, we search for the name snd qid.elt in the opened modules of st. The boolean b only indicates if the error message should mention variables, in the case where the module path is empty and the symbol is unbound. This is reported using the Fatal exception. Term.expo.Protec symbols from other modules are allowed in left-hand side of rewrite rules (only) iff ~prt is true. Term.expo.Privat symbols are allowed iff ~prv is true.