From: Michael Heerdegen <michael_heerdegen@web.de>
To: daanturo <daanturo@gmail.com>
Cc: 49316@debbugs.gnu.org
Subject: bug#49316: Add apply-partially's right version
Date: Sat, 03 Jul 2021 05:06:18 +0200 [thread overview]
Message-ID: <875yxsxfit.fsf@web.de> (raw)
In-Reply-To: <5a08f089-3a19-d747-5098-4751c92a5b79@gmail.com> (daanturo@gmail.com's message of "Fri, 2 Jul 2021 11:39:03 +0700")
daanturo <daanturo@gmail.com> writes:
> +(defun apply-mid-partially (fun position &rest args)
> + "Return a function that is a partial application of FUN to ARGS at POSITION.
I'm not sure if I would prefer that. Personally I guess I would like
something like this instead: A macro that allows partial application
that really looks like an application.
A placeholder (e.g. the symbol `_' which should normally be unbound)
stands for an argument that is used from the args provided in the actual
call:
#+begin_src emacs-lisp
(defmacro applying-partially (call)
(let ((args (make-symbol "args")))
`(lambda (&rest ,args)
(apply #',(car call)
,@(mapcar (lambda (arg)
(if (eq arg '_)
`(pop ,args)
arg))
(cdr call))
,args))))
(defalias 'minus-10 (applying-partially (- _ 10)))
(minus-10 120) ;; ==> 110
(defalias 'my-list-with-some-elts
(applying-partially (list 0 _ 2 _ 4)))
(my-list-with-some-elts 'a 'b 'c 'd) ; => (0 a 2 b 4 c d)
(symbol-function 'my-list-with-some-elts)
;; => (closure (t) (&rest args)
;; (apply #'list 0 (pop args) 2 (pop args) 4 args))
#+end_src
In my eyes that would be more general and a bit better readable (I like
when eldoc works with such stuff).
Regards,
Michael.
next prev parent reply other threads:[~2021-07-03 3:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 12:40 bug#49316: Add apply-partially's right version daanturo
2021-07-01 13:11 ` Basil L. Contovounesios
2021-07-01 16:24 ` daanturo
2021-07-01 17:06 ` daanturo
2021-07-01 17:16 ` daanturo
2021-07-01 18:45 ` Eli Zaretskii
2021-07-02 2:49 ` daanturo
2021-07-03 7:03 ` Eli Zaretskii
2021-10-24 6:55 ` Stefan Kangas
2021-10-24 10:49 ` daanturo
2021-10-24 11:18 ` Stefan Kangas
2021-10-24 12:13 ` Eli Zaretskii
2021-10-24 13:47 ` Lars Ingebrigtsen
2021-10-24 14:10 ` Stefan Kangas
2021-10-24 14:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-25 12:50 ` Lars Ingebrigtsen
2021-10-24 13:38 ` Lars Ingebrigtsen
2021-07-02 16:32 ` daanturo
2021-07-03 7:03 ` Eli Zaretskii
2021-07-01 22:34 ` Michael Heerdegen
2021-07-02 4:39 ` daanturo
2021-07-03 3:06 ` Michael Heerdegen [this message]
2021-07-03 6:17 ` daanturo
2021-07-03 14:13 ` Phil Sainty
2021-07-05 4:29 ` daanturo
2021-07-05 12:02 ` Phil Sainty
2021-07-06 4:33 ` Michael Heerdegen
2021-07-07 16:30 ` daanturo
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=875yxsxfit.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=49316@debbugs.gnu.org \
--cc=daanturo@gmail.com \
/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).