From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: can lei require Inline::C?
Date: Tue, 2 Feb 2021 10:09:02 +0000 [thread overview]
Message-ID: <20210202100902.GA1438@dcvr> (raw)
Performance and interactivity suck without being able to use FD
passing (especially tab completions). And having to maintain
and separate code paths is a huge time sink...
Inline::C is packaged by every relevant distro (unlike
Socket::Msghdr), and I figure anybody who uses lei at this stage
will have a C compiler...
It would let us use io-uring and maybe some other things
more easily, too (and I miss hacking in C).
next reply other threads:[~2021-02-02 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 10:09 Eric Wong [this message]
2021-02-03 0:02 ` can lei require Inline::C? Kyle Meyer
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210202100902.GA1438@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.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).