public inbox for yew-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Yew framework devel list at Proxmox"
	<yew-devel@lists.proxmox.com>,
	"Dominik Csapak" <d.csapak@proxmox.com>
Subject: Re: [yew-devel] [PATCH yew-widget-toolkit v1 1/2] store: use try_borrow and expect_throw for better error messages
Date: Tue, 06 May 2025 14:26:19 +0200	[thread overview]
Message-ID: <D9P2RLFBAG4P.2F38VPJUNR0E1@proxmox.com> (raw)
In-Reply-To: <4cf65416-049f-496a-8f8a-cdce4b7d1c8b@proxmox.com>

On Tue May 6, 2025 at 2:21 PM CEST, Dominik Csapak wrote:
> On 5/6/25 13:54, Shannon Sterz wrote:
>> this makes use of the `UnwrapThrowExt` trait to improve error messages
>
> nit: this is not true anymore in v1
>
> could maybe fixed up on applying though

yes missed that sorry, will send a v2

>
>> when acquring store locks. taking such locks in async functions can
>> sometimes lead to bugs that can be unreliably reproduced, this should
>> provide more information about the source of the error compared to
>> just panicking.
>>
>> Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
>> ---
>>   src/state/store.rs | 11 +++++++++--
>>   1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/src/state/store.rs b/src/state/store.rs
>> index bde7d9da..67e72b77 100644
>> --- a/src/state/store.rs
>> +++ b/src/state/store.rs
>> @@ -130,7 +130,10 @@ impl<T: 'static> Store<T> {
>>       /// Panics if the value is currently mutably locked.
>>       pub fn read(&self) -> StoreReadGuard<T> {
>>           StoreReadGuard {
>> -            state: self.inner.borrow(),
>> +            state: self
>> +                .inner
>> +                .try_borrow()
>> +                .expect("Could not acquire read lock on store!"),
>>           }
>>       }
>>
>> @@ -142,7 +145,11 @@ impl<T: 'static> Store<T> {
>>       /// When the returned [StoreWriteGuard] is dropped, the store listeners
>>       /// are notified. To prevent that use [StoreWriteGuard::skip_update]
>>       pub fn write(&self) -> StoreWriteGuard<T> {
>> -        let state = self.inner.borrow_mut();
>> +        let state = self
>> +            .inner
>> +            .try_borrow_mut()
>> +            .expect("Could not acquire write lock on store!");
>> +
>>           StoreWriteGuard {
>>               state,
>>               update: true,
>
>
>
> _______________________________________________
> yew-devel mailing list
> yew-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel



_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel


      reply	other threads:[~2025-05-06 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 11:54 Shannon Sterz
2025-05-06 11:54 ` [yew-devel] [PATCH yew-widget-toolkit v1 2/2] store: add try_read() and try_write() functions Shannon Sterz
2025-05-06 12:21 ` [yew-devel] [PATCH yew-widget-toolkit v1 1/2] store: use try_borrow and expect_throw for better error messages Dominik Csapak
2025-05-06 12:26   ` Shannon Sterz [this message]

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=D9P2RLFBAG4P.2F38VPJUNR0E1@proxmox.com \
    --to=s.sterz@proxmox.com \
    --cc=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 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