unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Package.el and specifying alternative dependencies
Date: Wed, 12 Apr 2017 09:44:32 +0200	[thread overview]
Message-ID: <87h91ukr33.fsf@zigzag> (raw)
In-Reply-To: <CAFyQvY27g_TbZPUCcV6uPS36vspD0ooLWfwou0EDPZ9C3LvpxQ@mail.gmail.com> (Kaushal Modi's message of "Tue, 11 Apr 2017 22:37:29 +0000")

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]


() Kaushal Modi <kaushal.modi@gmail.com>
() Tue, 11 Apr 2017 22:37:29 +0000

       ;; It's *very* critical that the order of packages stays
       ;; the same in NEW-RET as in ORIG-RET. The `push' command
       ;; flips the order, so use `reverse' to flip the order
       ;; back to the original.

If you don't mind ‘cl’, you can also use ‘cl-remove-if’ instead.
Squinting a little, i see the removal predicate is essentially
set membership, which seems to indicate ‘cl-set-difference’.
Unfortunately, a quick scan of (info "(cl) Lists as Sets")
reveals no guarantees on order, and Common Lisp (per CLHS)
actively disclaims such guarantees.  So it goes...

-- 
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)
   (pcase (context query)
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2017-04-12  7:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03  0:41 Package.el and specifying alternative dependencies Tim Cross
2017-03-04 21:57 ` Mark Oteiza
2017-03-04 22:32   ` Tim Cross
2017-03-04 22:46 ` Kaushal Modi
2017-03-04 23:44   ` Tim Cross
2017-04-11 22:37     ` Kaushal Modi
2017-04-12  7:35       ` Tim Cross
2017-04-12  7:44       ` Thien-Thi Nguyen [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

  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=87h91ukr33.fsf@zigzag \
    --to=ttn@gnu.org \
    --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 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).