package dune-rpc
Communicate with dune using rpc
Install
Dune Dependency
Authors
Maintainers
Sources
dune-3.8.0.tbz
sha256=f7e2970bfab99c7766ff1a05deff5ad7f82cb2471abca6f72449572293f5f6b4
sha512=3b3a566f63842c314de2c0a660c5f7714bc90f8303c82d82e3021aee84980eff1886d15c9b9d4ea0047a411d799fb39d5f2ea70a92bdeb629e00d3d5d5f2d994
doc/dune-rpc.private/Dune_rpc_private/Versioned/Make/Builder/index.html
Module Make.Builder
Source
A *declaration* of a procedure is a claim that this side of the session is able to *initiate* that procedure. Correspondingly, *implementing* a procedure enables you to *receive* that procedure (and probably do something in response).
Currently, attempting to both implement and declare the same procedure in the same builder will raise. While there is nothing fundamentally wrong with allowing this, it is simpler for the initial version negotiation to treat all method names uniformly, rather than specifying whether a given (set of) generation(s) is implemented or declared.
Finally, attempting to declare or implement the same generation twice will also raise.
Source
val implement_notification :
'state t ->
'payload Decl.notification ->
('state -> 'payload -> unit Fiber.t) ->
unit
Source
val implement_request :
'state t ->
('req, 'resp) Decl.request ->
('state -> 'req -> 'resp Fiber.t) ->
unit
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>