From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Mattias_Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.devel Subject: Bootstrap/autoload policy (was Re: regular expressions that match nothing) Date: Mon, 20 May 2019 18:26:04 +0200 Message-ID: References: <7a6b23f52418b093a4cf7a6db4306cf425533249.camel@acm.org> <87a7fnzd3u.fsf@web.de> <128EBFB8-78FF-47C3-8F28-C1EF91BFC4BB@acm.org> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="233719"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Stefan Monnier To: Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 20 18:36:13 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hSlGm-000ydu-Vc for ged-emacs-devel@m.gmane.org; Mon, 20 May 2019 18:36:13 +0200 Original-Received: from localhost ([127.0.0.1]:38346 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hSlGl-0000Np-Vf for ged-emacs-devel@m.gmane.org; Mon, 20 May 2019 12:36:12 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:42146) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hSl76-0000s5-7P for emacs-devel@gnu.org; Mon, 20 May 2019 12:26:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hSl75-0000YD-8s for emacs-devel@gnu.org; Mon, 20 May 2019 12:26:12 -0400 Original-Received: from mail214c50.megamailservers.eu ([91.136.10.224]:54598 helo=mail193c50.megamailservers.eu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hSl73-0000Wl-OX for emacs-devel@gnu.org; Mon, 20 May 2019 12:26:11 -0400 X-Authenticated-User: mattiase@bredband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1558369567; bh=oBXhhbAsi4CutU1UbZj+vGifA3OsdCj7qpaQhhDNpEc=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=atZMpnlc+lGlSg/2HvCm7HfH7R2LalojmB13XVifqUq2z9SoCIv+bsvnV591JpLcW Dh/+sDKDr+ozAfqH1fxmHXwjonEzzGI5Ek/q0IlHBIZXxk65YBHGxHXykjIF0JGsuR 6Q979v5giJB7sbmPCowu7+5Mx21Oxw5gzHOzFvLo= Feedback-ID: mattiase@acm.or Original-Received: from [192.168.0.4] ([188.150.171.71]) (authenticated bits=0) by mail193c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id x4KGQ4b3008527; Mon, 20 May 2019 16:26:06 +0000 In-Reply-To: <128EBFB8-78FF-47C3-8F28-C1EF91BFC4BB@acm.org> X-Mailer: Apple Mail (2.3445.104.11) X-CTCH-RefID: str=0001.0A0B0206.5CE2D51F.0006, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.3 cv=PM8hB8iC c=1 sm=1 tr=0 a=SF+I6pRkHZhrawxbOkkvaA==:117 a=SF+I6pRkHZhrawxbOkkvaA==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=N54-gffFAAAA:8 a=0_pqQzFkJpZSKUPwGDwA:9 a=QEXdDO2ut3YA:10 a=6l0D2HzqY3Epnrm8mE3f:22 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 91.136.10.224 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:236806 Archived-At: 15 maj 2019 kl. 23.07 skrev Mattias Engdeg=C3=A5rd : >=20 > We don't necessarily need a special form for it; we can just make = `(or)' work. >=20 > Proposed patch attached. (I also added its dual, (seq), since it would = be silly not to.) Na=C3=AFvely thinking the patch would be uncontroversial, I pushed it to = master only to see a bootstrap failure and I could use some policy = advice. The patch uses `cl-every' in rx.el, and the surface error (now fixed) = was that rx didn't require `cl-extra' where that function is defined, = despite it being autoloaded. (rx is pulled in from compile.el, from = bytecomp.el, from cl-generic.el, from loadup.el.) What I would like to know is whether the bootstrap was trying to tell me = something here. Was I wrong in using `cl-every' in the first place? How = do I know when to trust autoload, and when to use an explicit require? = Bootstrap after every change and see if it breaks?