Source
val mk_qual_typ :
standard:(module OaDocument.STANDARD) ->
vendor:(module OaDocument.VENDOR) ->
summary:OaSummary.t ->
OaTypes.schema ->
string
Source
val pp_construct_json :
(Restapis_o.Open__.Format.formatter -> 'a -> unit) ->
Restapis_o.Open__.Format.formatter ->
'a ->
unit
Source
val pp_destruct_json :
(Restapis_o.Open__.Format.formatter -> 'a -> unit) ->
Restapis_o.Open__.Format.formatter ->
'a ->
unit
Source
val pp_kind_to :
name_to:string ->
qual_typ:string ->
args:string ->
encoders:(module OaMlEncoders.S) ->
standard:(module OaDocument.STANDARD) ->
vendor:(module OaDocument.VENDOR) ->
summary:OaSummary.t ->
resolve_casename:(path:Json_query.path -> string) ->
depth:int ->
OaMlCompiler.t OaState.t ->
OaTypes.schema Fmt.t
Source
val pp_tag_of_kind :
standard:(module OaDocument.STANDARD) ->
vendor:(module OaDocument.VENDOR) ->
summary:OaSummary.t ->
match_:[ `MatchOptional | `MatchRequired | `NoMatch ] ->
resolve_casename:(path:Json_query.path -> string) ->
depth:int ->
OaTypes.schema_kind Fmt.t
Source
val pp_encoder_of_schema :
summary:OaSummary.t ->
(module OaMlEncoders.S) ->
OaMlCompiler.t OaState.t ->
Restapis_o.Open__.Format.formatter ->
OaTypes.schema ->
unit
include DkCoder_Std.SCRIPT
__init context
is the entry point for running a script module. The DkCoder compiler will inject this function at the top and bottom of the script module. The top __init
does nothing, while the bottom __init
calls the prior __init
.
That means:
- calling the
__init
function guarantees that the script module is initialized; that is, all of the script module's side-effects (ex.let () = Format.printf "Hello world@."
) are executed before the__init
returns to the caller. - you can override the
__init
function by simply defining the__init
idempotently. That will shadow the top__init
and when the bottom__init
is executed your__init
will be called instead of the do-nothing top__init
.
Future versions of DkCoder will call __init
in dependency order for all `You
script modules. Your __init
function may be called several times.
__repl context
is the entry point for debugging a script module in a REPL. The DkCoder compiler will inject this function at the top and bottom of the script module. The top __repl
does nothing, while the bottom __repl
calls the prior __repl
.
That means:
- you can override the
__repl
function by simply defining the__repl
idempotently. That will shadow the top__repl
and when the bottom__repl
is executed your__repl
will be called instead of the do-nothing top__repl
.
The run-time module information for the script module.