Backend profiles and their registry — the DIP swap point.
A profile is plain data describing what one transport does with each verb.
Adding a third transport is register! of one more profile; nothing above
this namespace changes.
The :slynk profile's RPC names and argument lists were measured against a running image, and the package qualifications are load bearing.
Backend profiles and their registry — the DIP swap point. A profile is plain data describing what one transport does with each verb. Adding a third transport is `register!` of one more profile; nothing above this namespace changes. The :slynk profile's RPC names and argument lists were measured against a running image, and the package qualifications are load bearing.
(backends)Registered backend ids, sorted.
Registered backend ids, sorted.
(capabilities backend-id)Verbs BACKEND-ID serves, sorted. Empty when the backend is unregistered.
Verbs BACKEND-ID serves, sorted. Empty when the backend is unregistered.
nREPL, driven through CIDER. Verbs map to nREPL op names.
:inspect and :restart are absent: CIDER exposes both, but neither has been measured here, and an unmeasured op is not a capability.
nREPL, driven through CIDER. Verbs map to nREPL op names. :inspect and :restart are absent: CIDER exposes both, but neither has been measured here, and an unmeasured op is not a capability.
Profiles registered at load time, in registry order.
Profiles registered at load time, in registry order.
(profile backend-id)The profile registered under BACKEND-ID, or nil.
The profile registered under BACKEND-ID, or nil.
(register! profile)Register PROFILE under its id, replacing any profile sharing it. Returns the id. Throws when PROFILE does not conform to schema/Profile.
Register PROFILE under its id, replacing any profile sharing it. Returns the id. Throws when PROFILE does not conform to schema/Profile.
(reset-registry!)Restore the registry to default-profiles. For fixtures.
Restore the registry to `default-profiles`. For fixtures.
SLY/Slynk, driven against a Common Lisp image.
slynk-completion: and slynk-apropos: are separate packages from slynk:
and resolve only after :profile/prelude has been required. An op whose
package has not been loaded does not signal — the request never receives a
reply — so the prelude is a correctness requirement, not an optimisation.
:eval uses eval-and-grab-output so a form's stdout reaches the caller alongside its value.
SLY/Slynk, driven against a Common Lisp image. `slynk-completion:` and `slynk-apropos:` are separate packages from `slynk:` and resolve only after :profile/prelude has been required. An op whose package has not been loaded does not signal — the request never receives a reply — so the prelude is a correctness requirement, not an optimisation. :eval uses eval-and-grab-output so a form's stdout reaches the caller alongside its value.
(supports? backend-id verb)Does BACKEND-ID serve VERB?
Does BACKEND-ID serve VERB?
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |