From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Imports / inclusion of s.el into Emacs Date: Sat, 02 May 2020 17:09:11 -0400 Message-ID: References: <831ro2tqqx.fsf@gnu.org> <4a1fd3f4-df92-c756-9874-4d07b54148ac@yandex.ru> <3bd09dca-dcdc-7569-e5fb-f6b53397af9d@yandex.ru> <83bln6s5on.fsf@gnu.org> <6d43996b-65ab-0bc6-9124-156520396910@yandex.ru> <2152FEE0-987F-4816-9FB5-717EED2B47BE@icloud.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="4006"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel@gnu.org, joaotavora@gmail.com, rms@gnu.org, Dmitry Gutov To: =?utf-8?B?7KGw7ISx67mI?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 02 23:10:31 2020 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 1jUzP5-0000uu-9o for ged-emacs-devel@m.gmane-mx.org; Sat, 02 May 2020 23:10:31 +0200 Original-Received: from localhost ([::1]:33190 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jUzP4-0007QV-CI for ged-emacs-devel@m.gmane-mx.org; Sat, 02 May 2020 17:10:30 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45234) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jUzNw-0005wi-AR for emacs-devel@gnu.org; Sat, 02 May 2020 17:09:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jUzNv-0000dw-Mu for emacs-devel@gnu.org; Sat, 02 May 2020 17:09:19 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:6230) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jUzNt-0000bP-BP; Sat, 02 May 2020 17:09:17 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 1C85B100F40; Sat, 2 May 2020 17:09:14 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 8EEBE100EE7; Sat, 2 May 2020 17:09:12 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1588453752; bh=4h7PiFxu5RsJzvZqmi14tlsNrwZJ5+6SkQ06LlfiC04=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=ZJrXkpr1SN4LNsjEUieh3jvp6qWl6HoWuAFhiO9iMrqQoh821MUjOPOh0IP4gAs5A jkg6mrsfudSfiNcd13Ic1sCceKJHjsO9ge9fb/mRD5y+PEeciDrMf57uB5BhyjF95I yqPMn66EjlRVkjasV5BVn5x3UdBPpsUsFKz2WFfgPBTFejalMqjYUiPZ+UXERqGAq7 oEyydl2m6R7bdy9VMza2d4YVkOwJ7W/y2GZ333lg3+SnVMt8X7WlkIc92lSk4VBarK Ibuva/ISAUoi058IE8jd1kV8ZgmXRE4KG2xtDLm24yhFO1TYosywtgMh4OfEc0p7vn e/N5vAaqXX5Mw== Original-Received: from alfajor (unknown [216.154.3.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 44ED91205FE; Sat, 2 May 2020 17:09:12 -0400 (EDT) In-Reply-To: <2152FEE0-987F-4816-9FB5-717EED2B47BE@icloud.com> (=?utf-8?B?IuyhsOyEseu5iCIncw==?= message of "Sun, 3 May 2020 03:40:35 +0900") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/02 16:40:06 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 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:248571 Archived-At: > IMO a type prefix mostly makes sense when Using a naming based on the type of the arguments is a different convention than the one proposed here. We're proposing to use a *prefix* to group functions that are "related" by that prefix. It doesn't have to do with the type of the return value or the type of an argument. E.g. `match-string` doesn't take any regexp as argument but I'd be happy to put it under the `regexp-` or `re-` prefix (e.g. `regexp-submatch`). Stefan