From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: `aset` on strings, changing the size in bytes Date: Sun, 09 Sep 2018 09:26:07 +0300 Message-ID: <83in3fqj9c.fsf@gnu.org> References: <88must56x4.fsf@gnu.org> <83efe4trsa.fsf@gnu.org> <83lg8bsvfm.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1536474330 28694 195.159.176.226 (9 Sep 2018 06:25:30 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 9 Sep 2018 06:25:30 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 09 08:25:26 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fyt9w-0007Me-Jt for ged-emacs-devel@m.gmane.org; Sun, 09 Sep 2018 08:25:24 +0200 Original-Received: from localhost ([::1]:46248 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fytC3-0002ey-18 for ged-emacs-devel@m.gmane.org; Sun, 09 Sep 2018 02:27:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40749) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fytAp-0002dx-2D for emacs-devel@gnu.org; Sun, 09 Sep 2018 02:26:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fytAj-0006tu-6g for emacs-devel@gnu.org; Sun, 09 Sep 2018 02:26:18 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:33995) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fytAh-0006pa-9r; Sun, 09 Sep 2018 02:26:13 -0400 Original-Received: from [176.228.60.248] (port=4461 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fytAY-0000Jv-53; Sun, 09 Sep 2018 02:26:02 -0400 In-reply-to: (message from Richard Stallman on Sun, 09 Sep 2018 02:07:15 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:229547 Archived-At: > From: Richard Stallman > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Sun, 09 Sep 2018 02:07:15 -0400 > > > But if I'm mistaken, and the current implementation does cons a new > > string, then what is your problem with it? The original string is not > > mutable, it's just replaced wit ha new one. > > "Replaced with the new one" requires relocatable strings. Not necessarily, not in the example I've shown: (setq str (do-something-with str)) > But suppose we made a function like aset which returned > the string. That way, it could return a new string when necessary. > It would be used like > > (setq s (sset s idx newchar)) > > Or we could define it to replace a substring: > > (setq s (srep s from to newsubstring)) Why not have aset do this under the hood? Then we won't need to ask people to change code that worked for decades.