unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 69739@debbugs.gnu.org
Subject: bug#69739: 30.0.50; `type-of` is not precise enough
Date: Wed, 13 Mar 2024 13:55:33 +0200	[thread overview]
Message-ID: <86a5n2tkga.fsf@gnu.org> (raw)
In-Reply-To: <jwvbk7jpjze.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 12 Mar 2024 11:39:56 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 69739@debbugs.gnu.org
> Date: Tue, 12 Mar 2024 11:39:56 -0400
> 
> I think that marking it obsolete wouldn't be an option if the new
> function is named something like `cl-generic-type-of`: it would have to
> be a more "neutral" name.

I just picked up your own suggestion.  I'm not wedded to that name, so
if there are better alternatives, let's hear them.

> The reason why I'd like to make it obsolete (if it can't be changed) is
> to try and avoid having two slightly-different functions where most
> users don't actually care about the difference.

Sure, but we don't usually declare such APIs obsolete the very day the
better one is introduced.  We usually let the community some time to
adjust, and maybe tell us where our ideas were wrong or need some
adjustments.





  reply	other threads:[~2024-03-13 11:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 23:19 bug#69739: 30.0.50; `type-of` is not precise enough Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-12 13:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-12 14:40   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-12 16:07     ` Rudolf Schlatte
2024-03-13 22:10       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-12 13:58 ` Eli Zaretskii
2024-03-12 14:43   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-12 15:02     ` Eli Zaretskii
2024-03-12 15:39       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-13 11:55         ` Eli Zaretskii [this message]
2024-03-14 16:56           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15  9:42             ` Andrea Corallo
2024-03-15 10:54               ` Andrea Corallo
2024-03-15  9:51             ` Basil L. Contovounesios
2024-03-15 14:09               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 15:18                 ` Eli Zaretskii
2024-03-17 22:29                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-18 12:56                     ` Eli Zaretskii
2024-03-18 13:33                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 11:50             ` Eli Zaretskii

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=86a5n2tkga.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69739@debbugs.gnu.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 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).