From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: John Yates Newsgroups: gmane.emacs.help Subject: Re: Is it ok to sort a list of overlays destructively? Date: Thu, 29 Jul 2021 07:34:07 -0400 Message-ID: References: <87h7ggcov1.fsf@mbork.pl> <83bl6nvpcl.fsf@gnu.org> <87czr3ecpc.fsf@mbork.pl> <83wnpbtbsk.fsf@gnu.org> <87bl6ndlb3.fsf@mbork.pl> <83sfzyu0he.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30289"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Help Gnu Emacs mailing list To: Eli Zaretskii Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jul 29 13:53:36 2021 Return-path: Envelope-to: geh-help-gnu-emacs@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 1m94bY-0007gq-7g for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 29 Jul 2021 13:53:36 +0200 Original-Received: from localhost ([::1]:43318 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m94bX-0008Il-21 for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 29 Jul 2021 07:53:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46180) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m94Ix-0006cU-BF for help-gnu-emacs@gnu.org; Thu, 29 Jul 2021 07:34:23 -0400 Original-Received: from mail-ej1-f49.google.com ([209.85.218.49]:33734) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1m94Iv-0005Xq-LZ; Thu, 29 Jul 2021 07:34:22 -0400 Original-Received: by mail-ej1-f49.google.com with SMTP id hs10so1474927ejc.0; Thu, 29 Jul 2021 04:34:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=303dp/LcdL/7aRHczIjOgBU0cppRsSera88pWaClMgs=; b=nQLGe2DxW55Jp43bZddTAYKz7N9OA+HJsM1vh7i1xpnch/VDOBhzk6dJSXtXHNdgmd xTjHRSjpQiW05sLfJdBd/4NsOGvTiRbWwXUO93gPSJRHzuV82ohvKh2cpqwJMpNct6jb wNheaIWhjLjYF09wM3YRuB8EablmMmGd0IX08AsVCCmoEWbOJS38o9HC4qNeTagmi3YW REawo/awdXX9L0nxPswNV9cCG9D8RC04A5RQmwFWMrUS0Hh74+rxi3bLTYXCTCLB3I/F bxjn5sf91mRHnOlGwgeSgo5ko3rM4TKIsFNUVokDkBOQXwvgNGZrzZfUY2boat1LGqe4 A+gA== X-Gm-Message-State: AOAM531N4fAZiNwoj7KuXCg6hARhgvLlklmqPiI/RFsMLxXZCgdk74q4 X9euENwI+sq66RGnXZgWuflqkviM84nSrrrSbS+dJaqMJQ4= X-Google-Smtp-Source: ABdhPJymOKiW6Bz3sYZSGAI11LlharJvjyjn0/TS6JOmsO6wSjb7Y3vXsr5+JI8YN+dzOJ0FnH3i/D9OpPaQ6SxHNQ0= X-Received: by 2002:a17:906:3499:: with SMTP id g25mr4194469ejb.471.1627558458952; Thu, 29 Jul 2021 04:34:18 -0700 (PDT) In-Reply-To: <83sfzyu0he.fsf@gnu.org> Received-SPF: pass client-ip=209.85.218.49; envelope-from=john.yates.sheets@gmail.com; helo=mail-ej1-f49.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:132173 Archived-At: On Wed, Jul 28, 2021 at 7:44 AM Eli Zaretskii wrote: > > Basically, you should assume that Emacs protects itself where that is > needed, so if it handed you a list or some other data, and nothing in > the doc string warns you against doing something with that data, you > are free to do that, and if that causes unexpected results, there's > either a documentation bug or a code bug that needs to be fixed. I am not sure if such a statement exists in any of the manuals. Should it not be stated explicitly somewhere?