From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Proposal: Forwards-Compatibility Library for Emacs Date: Tue, 21 Sep 2021 15:24:02 -0400 Message-ID: References: <877dfavmzw.fsf@posteo.net> <87czp2c6qd.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8825"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Philip Kaludercic , emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Sep 21 21:25:29 2021 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 1mSlOR-00023y-KS for ged-emacs-devel@m.gmane-mx.org; Tue, 21 Sep 2021 21:25:27 +0200 Original-Received: from localhost ([::1]:45924 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mSlOQ-0001Bc-9Z for ged-emacs-devel@m.gmane-mx.org; Tue, 21 Sep 2021 15:25:26 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35450) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mSlNf-0000Tl-M8 for emacs-devel@gnu.org; Tue, 21 Sep 2021 15:24:39 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:11609) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mSlNc-0002fn-By for emacs-devel@gnu.org; Tue, 21 Sep 2021 15:24:38 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 357B0441327; Tue, 21 Sep 2021 15:24:34 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id BE77D441324; Tue, 21 Sep 2021 15:24:32 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1632252272; bh=IZf7nqK+vKSzmws2lHefNojC27fpdM+fHCzpXZLzGhM=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=WL2hLJDEfrCXGNOswSQYeluz+thohQoMvQoqz5ELlu1TR3zEzUOksocDyhWI7lqpG DS+p7gs2XoWbk8nPxNOy5QIH3FoHEN1cj7+Idam5sdGEnXL+8Q107o2mTz9MyXIglT eh/MU5msEefrL4uq7qwWwxiBFiHfHoKlkGtOD7NXxEAEJY4qGn5z6qKn3iNaM9MewA hwgvaw+KHHPMJ0moZYruNEtzLGRp/0u/9NjPDBvHHxlYwNCMP52M9pONnnCQUOWyLt KrtAyG8ig8jVtvfOyhlKbObLBPzvzQ5QJ0CAgCaMhgbd1ycJKKzYD+X34UQF9crLkJ /f9RiT6ElMd7w== Original-Received: from alfajor (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id AF062120228; Tue, 21 Sep 2021 15:24:32 -0400 (EDT) In-Reply-To: <87czp2c6qd.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 21 Sep 2021 17:02:02 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:275265 Archived-At: > The point here is to not to have any separate namespace, so that you can > just can put core packages into ELPA without doing any rewrites. > What's the concrete risk here? I think in practice it's usually not a problem, but I'd be surprised if there aren't counter examples. So for a library that wants to do it in a somewhat predictable/systematic way, I think it's much simple to have all the definitions in a specific namespace (like `compat28-`), and then it's a small matter of have a trivial `compat28.el` library that comes with Emacs-28 which has a bunch of `defalias`. The main advantage is that we then don't need to assess the possible risks at all, so we're free to think about the things that actually matter. Stefan