unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Generic functions: Specializers like `or' or `memq'?
Date: Sun, 21 Nov 2021 14:43:58 -0500	[thread overview]
Message-ID: <jwvtug5s3ic.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87v914lorv.fsf@web.de

Michael Heerdegen [2021-11-07 02:48:04] wrote:
> Stefan Monnier via Users list for the GNU Emacs text editor
> <help-gnu-emacs@gnu.org> writes:
>
>>     (or (eql 4) integer)
>> and
>>     (or (eql 4) (eql 5))
>> and
>>     (or (eql 4) (eql "hello"))
>
> That's not a good example for how specializers I wanted to be able to
> write would look like, but I see the problem.

BTW, the above problem doesn't prevent defining an `or` specializer.
It just means that this specializer may not always behave quite like one
might expect :-(

I think a `memql` specializer would be easier and less likely to cause
problems: you could just give it a priority just below that of `eql`
(it may still get it wrong in that (memql true false maybe) would likely
get higher priority than a specializer like `boolean` which (if we were
to add such a type) would like only match `nil` and `t` and hence
should ideally have higher priorty instead).

Feel free to give us some concrete examples of the kinds of things you'd
like to do, if you want to see what it would take to support them.


        Stefan




  reply	other threads:[~2021-11-21 19:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 17:17 Generic functions: Specializers like `or' or `memq'? Michael Heerdegen
2021-11-03 18:21 ` Philip Kaludercic
2021-11-03 21:10   ` Michael Heerdegen
2021-11-03 21:32     ` Eric Abrahamsen
2021-11-03 23:19       ` Michael Heerdegen
2021-11-03 23:38         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-04  0:26           ` Michael Heerdegen
2021-11-04  1:31       ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-04  2:34         ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-04  4:01           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-06 22:32         ` Michael Heerdegen
2021-11-06 23:36           ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-07  1:48             ` Michael Heerdegen
2021-11-21 19:43               ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2021-11-23  8:16                 ` Michael Heerdegen
  -- strict thread matches above, loose matches on Subject: below --
2021-11-04 17:31 Eric Abrahamsen
2021-11-05 21:17 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-05 21:36   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-06 23:29     ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-06 23:52       ` Emanuel Berg via Users list for the GNU Emacs text editor

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=jwvtug5s3ic.fsf-monnier+emacs@gnu.org \
    --to=help-gnu-emacs@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.
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).