From: Shannon Sterz <s.sterz@proxmox.com>
To: yew-devel@lists.proxmox.com
Subject: [yew-devel] [PATCH yew-widget-toolkit v2 0/2] improve error message on store locks and add non-panicking functions
Date: Tue, 6 May 2025 14:44:43 +0200 [thread overview]
Message-ID: <20250506124445.196798-1-s.sterz@proxmox.com> (raw)
this series adds more context to a locking failure in the first commit.
the second commit then adds functions that allow components to recover
from not being able to acquire a lock, instead of simply panicking.
--
changes since v1 (thanks @ Dominik):
- rephrase the commit message of the first commit
changes since rfc:
- don't use `UnwrapThrowExt` as it does not improve error handling
meaningfully. (thanks @ Dominik)
- add `try_read()` and `try_write()` functions to allow components to
recover from not being able to acquire a lock instead of panicking.
--
Shannon Sterz (2):
store: use try_borrow and expect for better error messages
store: add try_read() and try_write() functions
src/state/store.rs | 32 +++++++++++++++++++++++++-------
1 file changed, 25 insertions(+), 7 deletions(-)
--
2.39.5
_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel
next reply other threads:[~2025-05-06 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 12:44 Shannon Sterz [this message]
2025-05-06 12:44 ` [yew-devel] [PATCH yew-widget-toolkit v2 1/2] store: use try_borrow and expect for better error messages Shannon Sterz
2025-05-06 12:44 ` [yew-devel] [PATCH yew-widget-toolkit v2 2/2] store: add try_read() and try_write() functions Shannon Sterz
2025-05-07 8:25 ` [yew-devel] applied: [PATCH yew-widget-toolkit v2 0/2] improve error message on store locks and add non-panicking functions 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=20250506124445.196798-1-s.sterz@proxmox.com \
--to=s.sterz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal