From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id F047A1FF17E for ; Thu, 11 Dec 2025 14:49:48 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8DBC016B4D; Thu, 11 Dec 2025 14:50:30 +0100 (CET) MIME-Version: 1.0 Date: Thu, 11 Dec 2025 13:49:35 +0000 In-Reply-To: <20251211125934.2358700-1-d.csapak@proxmox.com> References: <20251211125934.2358700-1-d.csapak@proxmox.com> X-Mailer: BlueMind-MailApp-v5 Message-ID: From: Dietmar Maurer To: Yew framework devel list at Proxmox X-Bm-Parsing-Options: encoded-parts X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1765460994534 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.323 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy HTML_MESSAGE 0.001 HTML included in message KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [yew-devel] [PATCH yew-widget-toolkit] props: replace `BuilderFn` with `RenderFn` X-BeenThere: yew-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Yew framework devel list at Proxmox List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Yew framework devel list at Proxmox Content-Type: multipart/mixed; boundary="===============7206877789183119728==" Errors-To: yew-devel-bounces@lists.proxmox.com Sender: "yew-devel" --===============7206877789183119728== Content-Type: multipart/alternative; boundary="-=Part.1bc.ab0f71b0de158f40.19b0dac9697.7175998b6c2b4a7f=-" ---=Part.1bc.ab0f71b0de158f40.19b0dac9697.7175998b6c2b4a7f=- Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I think this was the reason I invented the whole thing=2E > The only slightly awkward changes are: * we now have to use `apply(&())`= in this case * when giving a callback to such a builder we have to use `|_= : &_|` now, but this was also the case for any closure that got converted i= nto a `RenderFn`=2E Being forced to use |_: &_| is ugly, and the compiler errors for that are = even more ugly and confusing=2E So I am not sure about this change=2E ---=Part.1bc.ab0f71b0de158f40.19b0dac9697.7175998b6c2b4a7f=- Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

I think this was the reason I invented the whole thing=2E

> The only slightly awkward changes are: * we now ha= ve to use `apply(&())` in this case * when giving a callback to such a = builder we have to use `|_: &_|` now,  but this was also the case= for any closure that got converted into a  `RenderFn`=2E

Being forced to use |_: &_|=  is ugly,= and the compiler errors for that are even more ugly and confusing=2E So I = am not sure about this change=2E
---=Part.1bc.ab0f71b0de158f40.19b0dac9697.7175998b6c2b4a7f=--- --===============7206877789183119728== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ yew-devel mailing list yew-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel --===============7206877789183119728==--