unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: poptsov.artyom@gmail.com (Artyom V. Poptsov)
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: Guile Users' Mailing List <guile-user@gnu.org>
Subject: Re: [ANN] Metabash 0.0.0
Date: Sat, 08 Aug 2020 10:32:23 +0300	[thread overview]
Message-ID: <87y2mpa8zc.fsf@gmail.com> (raw)
In-Reply-To: <CA+XASoVsJax7q-LJ0JvPHsYrZSXv+MTn9F-svJ0_5TGBsvGn3Q@mail.gmail.com> ("Aleix Conchillo \=\?utf-8\?Q\?Flaqu\=C3\=A9\=22's\?\= message of "Fri, 7 Aug 2020 11:15:05 -0700")

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

> This is really cool!

Thanks!

> Maybe it doesn't make sense, but could the `(guile ...) be handled by
> the same running process instead of creating another process, so you
> just pass this to the plumber?

Yes, it makes sense when a Guile code runs locally; it could be possible
to run the code in a different thread instead of spawning a new Guile
process.

On the other hand, I'd love to have uniformity in the way the Guile code
is handled in the pipeline, either locally or remotely; that also means
when executed locally it does not affected by the current program state
and cannot modify in any way as it would be if I'd run it in a new
thread.

Nevertheless, big thanks for thought-provoking suggestions and the
patch (I merged it today.)

- Artyom

-- 
Artyom "avp" Poptsov <poptsov.artyom@gmail.com>
CADR Hackerspace co-founder: https://cadrspace.ru/
GPG: D0C2 EAC1 3310 822D 98DE  B57C E9C5 A2D9 0898 A02F

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2020-08-08  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 20:35 [ANN] Metabash 0.0.0 Artyom V. Poptsov
2020-08-07 18:15 ` Aleix Conchillo Flaqué
2020-08-08  7:32   ` Artyom V. Poptsov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2mpa8zc.fsf@gmail.com \
    --to=poptsov.artyom@gmail.com \
    --cc=aconchillo@gmail.com \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).