Asynchronous Reliable Extensible Sleek RPC Server for Guile. First of all it's a library providing a lot of tools for evaluating and exploring the code, from simple reflection API to interruptible asyncronous evaluation. In addition to that it provides an async RPC server implementation based on nREPL protocol and can be used for programmable interactions with a running guile processes, for implementing REPLs, IDEs, test runners or other tools. It also can be potentially used as a backend or library for LSP server.

WARNING: It's in early stage of development, the API is a subject to change.

guile-ares-rs was previously known as guile-nrepl (because it started as just nREPL implementation in Guile Scheme). It was renamed to avoid any confusion with network/socket REPL, guile-ares-rs is not a usual REPL, it's actually not a REPL at all, it's an RPC Server, however it's possible to implement REPL-like experience with it (and respective client).

It's intended for use with Arei IDE, but you can use it with other generic nREPL clients.

The are multiple ways to utilize Ares RS, but most straightforward is to spawn a standalone server and connect to it from a client (Emacs Arei for example):

guix shell guile-next guile-ares-rs -- \
guile -c '((@ (ares server) run-nrepl-server))'

Don't forget to add your project source code and other dependencies to load path.

To be able to use G-expression special syntax #~, #$ and #$@ or when using Arei with Guix or other project, which have reader extensions, load reader extension before starting the nrepl server. You can find the explanation here.

guile -c \
"(begin (use-modules (guix gexp)) #;(load gexp reader extension globally) \
((@ (ares server) run-nrepl-server)))"

To learn more on how to setup a proper environment with exact version of Guix and channels available in the load path, take a look at sample-guile-project.

It depends, on fibers, and on guile-next (custom textual ports), tests are executed with gider.

Send patches to rde-devel mailing list in format: [PATCH guile-ares-rs 0/3] SUBJECT-HERE.

Send feedback to rde-discuss.

3.1. First Release Roadmap

3.2. Open Questions

One of the reasons this project started is unfortunate missbehave of current REPL soultions in different situation and here is a list of some of them:

• Text based REPL over socket is not interruptible.
• call/cc works when pasted into prompt of the repl, but fails when evaling from buffer with C-x C-e. (when saving continuation to symbol with set!)
• It's not possible to see stdout until evaluation completed.
• Gider tests hangs repl on errors.
• CAPF function is injected, even if there is no connection to REPL and throws errors preventing other CAPFs to work.
• There is no way to provide stdin input to running expression.
• Go to definition doesn't work for with-input-from-port.
• After using ,i in REPL, go to definition hangs up.
• Go to definition opens non-existing file.
• If expression being evaluated from buffer requires input from stdin it will be frozen.
• Rebinds M-. instead of using xref.
• https://spritely.institute/files/docs/guile-goblins/0.11.0/TEMPORARY-Live-hacking-_0060_0060fix_0027_0027.html
• https://www.reddit.com/r/scheme/comments/qyqxcd/geiser_sucks_is_there_a_way_to_make_it_suck_less/
• Comment by Olical, Conjure author on guile-ares-rs integration

5.1. NREPL

Q: Can I use guile-ares-rs with an existing network REPL?

A: Theoretically it's possible to upgrade existing REPL to guile-ares-rs, see bootstrap and infect modules (they can be not implemented yet).

Thanks for inspiration, help, support and motivation to Jos´e Antonio Ortega Ruiz, Nikita Domnitskii, Maxime Devos, Andy Wingo, Bozhidar Batsov, Andrey Listopadov, Dmitrii Bogdanov, David Thompson, Dmitry Polyakov.