From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Lisp files that load cl-lib in problematical ways Date: Thu, 19 Oct 2023 17:14:24 +0300 Message-ID: <83edhqu2bj.fsf@gnu.org> References: <87il8betof.fsf@dataswamp.org> <83fs3dgxv8.fsf@gnu.org> <835y38qvlg.fsf@gnu.org> <87bkcx6eci.fsf@dataswamp.org> <8734y7p7sz.fsf@dataswamp.org> <83v8b3mcuj.fsf@gnu.org> <87jzrjvze8.fsf@gmx.net> <83r0lrm4gj.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21225"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stephen.berman@gmx.net, incal@dataswamp.org, emacs-devel@gnu.org To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 19 16:15:20 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qtTo0-00058s-CA for ged-emacs-devel@m.gmane-mx.org; Thu, 19 Oct 2023 16:15:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qtTnG-0005Av-VF; Thu, 19 Oct 2023 10:14:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qtTnF-0005AS-6U for emacs-devel@gnu.org; Thu, 19 Oct 2023 10:14:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qtTnD-0006kF-Uq; Thu, 19 Oct 2023 10:14:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=0Xu1Zwknpb2fL9UZiE0QVaUvpbTD9AYk4CT6wbABhFw=; b=WfCOZewEQZfg L8V9RbuhqZw8AWXr+6Wo2Ubq233dLO7nHkQnuownoJrhKh8EMSRlkUiVEi00n4WOszFjAVpl9NDYP KsLNI5aJWOYL+jJSaN0D17H/rlILoOHhcz+c4QNgOXqzTPKVkED9h86tsqajXDaO5Mq748IcwzER7 BL9uJpceTYIYQklEjC9qQcCCnw1fou+fFOmuu2yA5+btBdpsMpGnEkx/0L4XEQc9+vgGPKlWaEk4P UMSjSnWmGzsMVFRarXE1On8rt9+7mXYLD2VBNxsUUdunCxHFQ+is37/smM6elXKcN2mqC47fk8NfR FQtZ6qgrioNmcyo00SRdng==; In-Reply-To: (message from Andrea Corallo on Thu, 19 Oct 2023 09:44:51 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:311598 Archived-At: > From: Andrea Corallo > Cc: Stephen Berman , incal@dataswamp.org, > emacs-devel@gnu.org > Date: Thu, 19 Oct 2023 09:44:51 -0400 > > Okay, I confirm that comp.el loads cl-lib, so any jit compilation > triggered loads that. This is OK, not a problem. > OTOH one thing we could do, if that's important, is to split the code > that only drives the async compilation (that actually happens in a > subprocess) so we don't load cl-lib in the Emacs the user is actually > using. This should not be that hard (optimism mode on). I don't see the need, but I will not object if you want to make such changes.