all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Davis Herring <herring@lanl.gov>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Artur Malabarba <bruce.connor.am@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] scratch/package-fix e5d5cdf 1/2:	emacs-lisp/package.el: Indicate incompatible packages.
Date: Thu, 12 Feb 2015 09:35:08 -0700	[thread overview]
Message-ID: <54DCD63C.5090000@lanl.gov> (raw)
In-Reply-To: <jwvmw4jjiyo.fsf-monnier+emacsdiffs@gnu.org>

> The algorithmic problem is quite real, indeed.
> We could solve it by adding a "compatible" field to the struct, which
> we'd set to `yes' or `no' (so as to memoize previous computations), so
> the complexity would stay linear in the number of packages (though also
> linear in the number of number of `requires').

The compatible flag need not be added to the struct; it could instead be
maintained in a hash table retained only for the duration of printing.
(Then it has to be recomputed once per listing, but as it's linear that
probably doesn't matter.)

Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.



  reply	other threads:[~2015-02-12 16:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150211170820.10979.16862@vcs.savannah.gnu.org>
     [not found] ` <E1YLalx-0002s8-E8@vcs.savannah.gnu.org>
2015-02-11 19:28   ` [Emacs-diffs] scratch/package-fix e5d5cdf 1/2: emacs-lisp/package.el: Indicate incompatible packages Stefan Monnier
2015-02-11 23:00     ` Artur Malabarba
2015-02-12 14:41       ` Stefan Monnier
2015-02-12 16:35         ` Davis Herring [this message]
2015-02-13 13:48           ` Artur Malabarba
2015-02-12 21:42         ` chad
2015-02-13 20:13           ` Stefan Monnier
2015-02-13 20:18             ` Artur Malabarba
2015-02-14 18:04               ` Artur Malabarba

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=54DCD63C.5090000@lanl.gov \
    --to=herring@lanl.gov \
    --cc=bruce.connor.am@gmail.com \
    --cc=emacs-devel@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 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.