From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: combining cond and let, to replace pcase. Date: Tue, 28 Nov 2023 10:55:01 -0500 Message-ID: References: <878r6u3s7f.fsf@web.de> <874jhh62db.fsf@neko.mail-host-address-is-not-set> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9263"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org To: =?windows-1252?B?Sm/jbyBU4XZvcmE=?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 28 16:56:05 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1r80RO-00025i-ON for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Nov 2023 16:56:02 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r80QZ-0007l9-IQ; Tue, 28 Nov 2023 10:55:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r80QX-0007ku-IW for emacs-devel@gnu.org; Tue, 28 Nov 2023 10:55:09 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r80QV-0008NM-94 for emacs-devel@gnu.org; Tue, 28 Nov 2023 10:55:09 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id ECE92807DB; Tue, 28 Nov 2023 10:55:02 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1701186902; bh=4JcYgSDhXXqj+6ng7BW83iB/NJREgzVnncPGiF8ri70=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=davaPG+bdc6kKnZSORVg5EFICrapSCSiYi8XYtE4ZNvCtfuk9i7rjvB2FQCmwn/Bz vghZZhqdzoJZm1OF0reqHKBq14MRnDezpnEKna5x7ArH/xNTe1FXd0HTN8K/hwIpmq siJ8yD2et8j2aYfmCM6kT+1Z2gKEjBZpbiCJQUp3cMRA33H/yQYjStRui9Qzpg06OZ UGDUTjPASsMkWBBOZLLLcbpI69/1kFnEuJcfONhjGZ+Ti73FCaCMT43Ciqc4Z4D8ip Z6W63D7eTUWIC/a+anLgU/dkcaQzZGyxhkSSFKrfchWblxcbG7PwwE3jXY6W+ymixG NfE1Oth9gPF/Q== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 1B5BF800E0; Tue, 28 Nov 2023 10:55:02 -0500 (EST) Original-Received: from pastel (unknown [45.72.194.97]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id ED19A1202CE; Tue, 28 Nov 2023 10:55:01 -0500 (EST) In-Reply-To: (=?windows-1252?Q?=22Jo=E3o_T=E1vora=22's?= message of "Tue, 28 Nov 2023 15:31:54 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313327 Archived-At: >> > that is why cl-loop and maybe pcase are "ugly" >> > one heuristic could be if autodoc can display something useful >> >> I suspect it would be difficult to do for `cl-loop` (would require heavy >> hacking on `cl-loop` itself), > > Would it? Isn't this more or less the same information that Edebug > already has for stepping through it? No, I think Eldoc on subexpressions inside `cl-loop` and `pcase` already work, the question was rather how to make Eldoc give tips about the macro's own syntax, e.g. when you're inside a `pred` or a `guard` display things like (guard BOOLEXP) or (pred FUN) and when you're after an `in` on `cl-loop` maybe something like PATTERN in LIST This info is not included in the Edebug specs :-( But you're right that maybe we could do that without too much extra work by adding that info to the Edebug spec. Stefan