unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Akib Azmain Turja <akib@disroot.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: cl-loop - do you understand it well?
Date: Sun, 11 Dec 2022 01:00:41 +0600	[thread overview]
Message-ID: <87wn6zhyna.fsf@disroot.org> (raw)
In-Reply-To: <87k02zkrzw.fsf@web.de> (Michael Heerdegen's message of "Sat, 10 Dec 2022 19:56:03 +0100")

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

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Emanuel Berg <incal@dataswamp.org> writes:
>
>> So what is this eval'd to - an why?
>
> The answer to the question in the subject is easier: No!
>
>
>> Hint: All and any method is allowed!
>>
>> ;;; -*- lexical-binding: t -*-
>>
>> (require 'cl-lib)
>>
>> (cl-loop
>>   for i from 0 to 1
>>   collect (lambda () i) into funs
>>   finally return (apply #'+ (mapcar #'funcall funs)) )

Somehow, the code doesn't make any sense to me.  What it's supposed to
achieve?

>
> Any method?  I would like to test it with Emacs 31.  Would it make a

Where did you get "Emacs 31"?  ;)

> difference?
>
> Honestly: Do the cl-loop fans think we should change the behavior?
>
>
> Michael.
>
>

-- 
Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5
Fediverse: akib@hostux.social
Codeberg: akib
emailselfdefense.fsf.org | "Nothing can be secure without encryption."

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

  reply	other threads:[~2022-12-10 19:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10  2:22 cl-loop - do you understand it well? Emanuel Berg
2022-12-10 18:56 ` Michael Heerdegen
2022-12-10 19:00   ` Akib Azmain Turja [this message]
2022-12-10 19:35     ` tomas
2022-12-10 20:48       ` Michael Heerdegen
2022-12-11  5:57         ` Akib Azmain Turja
2022-12-11 14:43           ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-12  6:03             ` Akib Azmain Turja
2022-12-12  1:41           ` Michael Heerdegen
2022-12-14 23:53             ` Emanuel Berg
2022-12-16  0:25               ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-17  0:02                 ` Emanuel Berg
2022-12-16  2:25               ` Michael Heerdegen
2022-12-17  0:03                 ` Emanuel Berg
2022-12-18  0:16                   ` Michael Heerdegen
2022-12-19 20:36                     ` Emanuel Berg
2022-12-21  8:12                       ` Michael Heerdegen

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=87wn6zhyna.fsf@disroot.org \
    --to=akib@disroot.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).