From: "Mattias Engdegård" <mattiase@acm.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 55395@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#55395: What does (1 2 3 . #2) mean?
Date: Mon, 23 May 2022 16:59:57 +0200 [thread overview]
Message-ID: <5EDC84C7-B886-4581-AE22-4DFA86DD1EE1@acm.org> (raw)
In-Reply-To: <jwvmtfefssm.fsf-monnier+emacs@gnu.org>
18 maj 2022 kl. 23.16 skrev Stefan Monnier <monnier@iro.umontreal.ca>:
>
>> [(1 2 3 . #0)]
>>
>> could mean either
>>
>> [#1=(1 2 3 . #1#)]
>>
>> or
>>
>> #1=[(1 2 3 . #1#)]
>
> AFAIK it *should* mean the latter (#0 is the root of the overall
> printed object, not just the list).
Yes, but the code was already a bit ambiguous in that respect. We don't keep track of the cons-level depth when printing; print_depth treats each list nesting as one step regardless of where in the list the nesting occurs. I suppose this could be remedied but I'm not going to work on it right now.
The previously attached patch has been pushed to master, on the grounds that it should be strictly better than what we had before; correctness should be back at the level before the change in circularity detection algorithm broke the tail index completely.
> Yup. But we don't shy away from playing the fools.
You know me, I don't even need to play one. It all comes natural.
next prev parent reply other threads:[~2022-05-23 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 11:32 bug#55395: What does (1 2 3 . #2) mean? Mattias Engdegård
2022-05-13 15:22 ` Lars Ingebrigtsen
2022-05-13 17:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-13 19:54 ` Lars Ingebrigtsen
2022-05-13 20:01 ` Mattias Engdegård
2022-05-14 13:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-18 14:29 ` Mattias Engdegård
2022-05-18 21:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 14:59 ` Mattias Engdegård [this message]
2022-05-13 16:08 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5EDC84C7-B886-4581-AE22-4DFA86DD1EE1@acm.org \
--to=mattiase@acm.org \
--cc=55395@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.