unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Lindqvist" <bjourne@gmail.com>
Cc: acm@muc.de, 74357@debbugs.gnu.org
Subject: bug#74357: c-mode: Some syntactic constructs cause unreasonable typing lag
Date: Sat, 16 Nov 2024 13:00:43 +0200	[thread overview]
Message-ID: <86ttc7h290.fsf@gnu.org> (raw)
In-Reply-To: <CALG+76fUCJR8n88DckX-KXJDeaHoiBJPerKyPfbZM97oiCXsog@mail.gmail.com> (message from Björn Lindqvist on Fri, 15 Nov 2024 22:43:45 +0100)

> From: Björn Lindqvist <bjourne@gmail.com>
> Date: Fri, 15 Nov 2024 22:43:45 +0100
> Cc: acm@muc.de, 74357@debbugs.gnu.org
> 
> Den fre 15 nov. 2024 kl 15:25 skrev Eli Zaretskii <eliz@gnu.org>:
> > Can you tell where in real life do you see such deeply-nested braces
> > in C source files?
> 
> 50 is perhaps exaggerating it, but in "modern" C++ with multiple
> namespaces, nested classes, and anonymous functions you can easily get
> scopes nested over a dozen levels deep.

Can you show such a file from a real-life project?  I'd like us to
have it as a means for judging real-life performance in these cases.

Thanks.





  reply	other threads:[~2024-11-16 11:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 20:39 bug#74357: c-mode: Some syntactic constructs cause unreasonable typing lag Björn Lindqvist
2024-11-15  7:40 ` Eli Zaretskii
2024-11-15 14:08   ` Björn Lindqvist
2024-11-15 14:25     ` Eli Zaretskii
2024-11-15 14:45       ` Alan Mackenzie
2024-11-15 21:43       ` Björn Lindqvist
2024-11-16 11:00         ` Eli Zaretskii [this message]
2024-11-28 20:03         ` Alan Mackenzie
2024-11-29 23:18           ` Alan Mackenzie
2024-11-30 18:04             ` Björn Lindqvist
2024-11-30 18:33               ` Alan Mackenzie
2024-11-30 20:07                 ` Björn Lindqvist
2024-12-01 17:49                   ` Alan Mackenzie

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86ttc7h290.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74357@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=bjourne@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).