all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 1fcc552: lisp/gnus/registry.el (registry-prune): Allow registry to reach full size before pruning
Date: Sat, 18 Apr 2015 10:34:24 -0400	[thread overview]
Message-ID: <874modo68f.fsf@lifelogs.com> (raw)
In-Reply-To: jwv1tjhv7wd.fsf-monnier+emacsdiffs@gnu.org

On Sat, 18 Apr 2015 10:20:30 -0400 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote: 

>> If initargs are to be avoided, maybe a compilation warning there would
>> be appropriate?[1]

SM> Agreed.  I haven't implemented one yet, but it's crossed my mind, yes.
SM> The main problem is that in (oref a b), the compiler has no idea what is
SM> the possible class(es) of `a', so it can't look up that class to see if
SM> `b' is an initarg.

SM> What I'm thinking of doing is keeping track of all known slot names and
SM> all known initarg names, and if `b' is an initarg name but not a slot
SM> name, then emit the warning.  This should work OK in practice since
SM> initargs tend to all be keywords, where slot names tend to all be
SM> non-keyword symbols.

That would work for me as a user, but I fear it will be pretty hard to
implement.

Ted




      reply	other threads:[~2015-04-18 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150320104953.20367.194@vcs.savannah.gnu.org>
     [not found] ` <E1YYuUz-0005J8-GO@vcs.savannah.gnu.org>
2015-03-20 14:35   ` [Emacs-diffs] master 1fcc552: lisp/gnus/registry.el (registry-prune): Allow registry to reach full size before pruning Stefan Monnier
2015-03-21  1:32     ` Eric Abrahamsen
2015-03-21  2:46       ` Stefan Monnier
2015-03-21 14:12         ` Eric Abrahamsen
2015-04-18 10:51     ` Ted Zlatanov
2015-04-18 14:20       ` Stefan Monnier
2015-04-18 14:34         ` Ted Zlatanov [this message]

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=874modo68f.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.org \
    /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.