From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 1B3A51F4B4; Tue, 2 Feb 2021 10:09:02 +0000 (UTC) Date: Tue, 2 Feb 2021 10:09:02 +0000 From: Eric Wong To: meta@public-inbox.org Subject: can lei require Inline::C? Message-ID: <20210202100902.GA1438@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: 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).