package dune-rpc
Communicate with dune using rpc
Install
Dune Dependency
Authors
Maintainers
Sources
dune-3.16.1.tbz
sha256=b781ae20f87613c2a11bd0717809e00470c82d615e15264f9a64e033051ac3de
sha512=fddf940d5634400fa14f6728235e0dba055b90a47f868d9fee80c9523b93fb2b9920a00e70dfdc5e1dd26a21d695ce854267b6a2ec305ce89ce9447733f7242c
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)"
>