From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.bugs Subject: bug#65017: 29.1; Byte compiler interaction with cl-lib function objects, removes symbol-function Date: Sun, 6 Aug 2023 12:47:15 +0200 Message-ID: References: <8B08E514-B2D5-48F5-BA90-4F5A9492F8F9@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.15\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12182"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Alan Mackenzie , 65017@debbugs.gnu.org, Eric Marsden To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Aug 06 12:48:18 2023 Return-path: Envelope-to: geb-bug-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 1qSbJ3-0002vl-RC for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 06 Aug 2023 12:48:17 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qSbIs-0004x6-2I; Sun, 06 Aug 2023 06:48:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qSbIp-0004wj-K1 for bug-gnu-emacs@gnu.org; Sun, 06 Aug 2023 06:48:03 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qSbIo-0007EH-8u for bug-gnu-emacs@gnu.org; Sun, 06 Aug 2023 06:48:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qSbIo-0006HO-5Q for bug-gnu-emacs@gnu.org; Sun, 06 Aug 2023 06:48:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 06 Aug 2023 10:48:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 65017 X-GNU-PR-Package: emacs Original-Received: via spool by 65017-submit@debbugs.gnu.org id=B65017.169131884723993 (code B ref 65017); Sun, 06 Aug 2023 10:48:02 +0000 Original-Received: (at 65017) by debbugs.gnu.org; 6 Aug 2023 10:47:27 +0000 Original-Received: from localhost ([127.0.0.1]:58708 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qSbIF-0006Ev-CZ for submit@debbugs.gnu.org; Sun, 06 Aug 2023 06:47:27 -0400 Original-Received: from mail-lf1-x134.google.com ([2a00:1450:4864:20::134]:62750) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qSbIB-0006Ee-IP for 65017@debbugs.gnu.org; Sun, 06 Aug 2023 06:47:26 -0400 Original-Received: by mail-lf1-x134.google.com with SMTP id 2adb3069b0e04-4fe45da0a89so5653326e87.1 for <65017@debbugs.gnu.org>; Sun, 06 Aug 2023 03:47:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691318837; x=1691923637; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:from:to:cc:subject :date:message-id:reply-to; bh=k23d1CquyqKsQoiy4tVy/HAx8gYSxCctMnvROHpzc9k=; b=Po7g9zJfdFGmL5cJTfHFESUFawSrJ1f+wMnoEuTTa+OVbzIc6Y1HjOwWWUhWEhRY1c UfI0DuALsh2TdzUw/aeMmf6Du4eIHRuaL3DJ+1FQvgkldc/mOoGjctptn2GI5oKZ35FX GVu6whCXGMki2gScuQW/Mum+wdhlv3QKuKcLmodMjPOHOFVfsWp/yq3TVY6yI8tDt8vy t3x2dtRi2K+QmVp3zz9jrCi12Jp9VEOLqT7+VXNlFYdCQ89B8iXtwO650MIwWIqg0eNg dx2uFezOhBTmJ7Pip2tXsWFfsMZKbIberxg11M2ehegFGjZMdFywF9vADkNW0QLowdkH Qm2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691318837; x=1691923637; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=k23d1CquyqKsQoiy4tVy/HAx8gYSxCctMnvROHpzc9k=; b=QlkHLLw/YtvKs65o9t8McpiPGvz2W+Kb4LzYLygcqr/jzn/8r+01uI3+UjjvLQ8Y8n jnXcFXv0XrzkRPVLed5WKVOjGEoYLZtTdwU4faRuk0rABgjqxWZ9BU0EvLT2egsA2uqL n3T1h3qVL6sWadFmcJGJgiWHCjER016HppoPsEVrkfHMK6HVeIgFXI1/kQxqPWT6jxb7 nvc4iFgNgYBaZ1BlqIBr/FUyL+635AzDsKkDiRar5KgAoJikBkOy/xDk89w8lzLjdilP oa+VjZV4N5OPN+l28eHrvs9EswD8sKr4PjQ6RORFGdxvt0SY2bQAbqgVRIOs9XeWqf98 VJyA== X-Gm-Message-State: AOJu0YwLdJDR10WHxCt0uz8oEEGj+qsHtg3DDirggTFiTSoOTt74mqUg XqOyUroePYZ5xTs85XvMkJU= X-Google-Smtp-Source: AGHT+IHw6lnt527WSH5O0529r15j7xJ8AJrRHbRfC27hnh+TB7KlmDMO/X+EZBBdsEVv2KEI83QfTw== X-Received: by 2002:a05:6512:ea3:b0:4fd:daa0:aed8 with SMTP id bi35-20020a0565120ea300b004fddaa0aed8mr1497067lfb.4.1691318837224; Sun, 06 Aug 2023 03:47:17 -0700 (PDT) Original-Received: from smtpclient.apple (c188-150-165-235.bredband.tele2.se. [188.150.165.235]) by smtp.gmail.com with ESMTPSA id a6-20020a19f806000000b004fe27229f55sm1066673lff.216.2023.08.06.03.47.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 06 Aug 2023 03:47:16 -0700 (PDT) In-Reply-To: X-Mailer: Apple Mail (2.3654.120.0.1.15) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:266847 Archived-At: 6 aug. 2023 kl. 00.40 skrev Stefan Monnier : >> Separate data structures for locations might be an option worth = exploring, >> keeping the actual s-expressions unadorned. Consider a reader mode = that also >> produces a table mapping cons cells read to their locations, for = example. >=20 > When Alan looked at it, the cost seemed prohibitive. I'm not aware of the details but think that it may be worth revisiting. The only serious difficulty a priori appears to be keeping locations in = transformed code, but most of our diagnostics are issued on code before = Lisp optimisations so this should mostly matter to macro-expansion. > BTW, a related option would be to develop a new kind of = macro-definition > along the lines of what's used in Scheme, where the macro author = doesn't > need to worry about such issues because the macro knows which parts of > the data it manipulates are chunks of code (potentially adorned with > metainfo) and can take care of extracting the underlying unadorned = code. Yes, Scheme doesn't have much problems with user code manipulating Lisp = as data. But what do actual Lisp compilers do? Do they perform a slow re-read = when until they get to the location they want, when they need to issue a = diagnostic? (Relint does something similar, in fact.)