From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id D62E61FF142 for ; Tue, 07 Apr 2026 10:48:47 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 58B0210BAE; Tue, 7 Apr 2026 10:49:22 +0200 (CEST) Message-ID: <72bd3973-955d-41a2-a735-9ebf3a3b98f2@proxmox.com> Date: Tue, 7 Apr 2026 10:49:16 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH yew-widget-toolkit v2] widget: add 'div' macro To: Thomas Lamprecht , Dominik Csapak , yew-devel@lists.proxmox.com References: <20260402134337.3433085-1-d.csapak@proxmox.com> <3570c013-8109-45cb-a054-7072fcea559e@proxmox.com> Content-Language: en-US From: Dietmar Maurer In-Reply-To: <3570c013-8109-45cb-a054-7072fcea559e@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1775551691046 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.337 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 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 Message-ID-Hash: 4Q2I3NZRPCCJBGLL6GWJII36LBVUQZAZ X-Message-ID-Hash: 4Q2I3NZRPCCJBGLL6GWJII36LBVUQZAZ X-MailFrom: dietmar@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Yew framework devel list at Proxmox List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: So far, I always found a way to restructure the rust code to make it readable, so Container::new().with_child("TEXT") was never a real problem. But I have to agree that it is too verbose. Maybe just a function named "div"? fn div(child: Into) -> Container { ... } > And it isn't exactly a plain div, as then one could just use the html! > macro from yew, so the name as is, is IMO not totally ideal. If we go > the macro way (what's Dietmars opinion on this?), I'd favor to call it > container! to better reflect that it uses the pwt container class. >