From: Dominik Csapak <d.csapak@proxmox.com>
To: yew-devel@lists.proxmox.com
Subject: [yew-devel] [PATCH yew-widget-toolkit 2/2] state: selection: make selection interface more consistent
Date: Wed, 29 Jan 2025 10:42:00 +0100 [thread overview]
Message-ID: <20250129094200.811682-2-d.csapak@proxmox.com> (raw)
In-Reply-To: <20250129094200.811682-1-d.csapak@proxmox.com>
due to the interior mutability of th Selection (it uses Rc<RefCell<>>),
we don't need the selection to be mutable when we select something. This
is reflected in in the interface for e.g. `select()` and `toggle()`
which only take a `&self`. For `bulk_select()` the same logic can be
applied, but it still took a `&mut self` which was not a problem, but it
was unnecessary. To make it more consistent, simply change from `&mut
self` to `&self`.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
src/state/selection.rs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/state/selection.rs b/src/state/selection.rs
index 21e8e85..6866436 100644
--- a/src/state/selection.rs
+++ b/src/state/selection.rs
@@ -151,7 +151,7 @@ impl Selection {
/// # Panics
///
/// If multiselect is false.
- pub fn bulk_select(&mut self, map: HashSet<Key>) {
+ pub fn bulk_select(&self, map: HashSet<Key>) {
self.inner.borrow_mut().bulk_select(map);
self.notify_listeners();
}
--
2.39.5
_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel
next prev parent reply other threads:[~2025-01-29 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 9:41 [yew-devel] [PATCH yew-widget-toolkit 1/2] widget: menu button: actually use 'disabled' property Dominik Csapak
2025-01-29 9:42 ` Dominik Csapak [this message]
2025-01-29 12:10 ` [yew-devel] applied: " Dietmar Maurer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250129094200.811682-2-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=yew-devel@lists.proxmox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.