You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, signals have two options for reading: read() and peek(). Both of these will panic if the signal's value has been dropped, but this can be prevented with try_read(). There is currently no way to do the same for peek().
Implement Suggestion
Add a way to peek signals without panicking if the underlying value has been dropped. Presumably this would live in the Readable trait with the other methods.
The text was updated successfully, but these errors were encountered:
Our implementation for Readable was inconsistent.
We had a try_unchecked variant for read but not for peek.
This resolves that by making a breaking change to the
Readable interface.
* Fix#2612: adjust readable trait to allow try_peek
Our implementation for Readable was inconsistent.
We had a try_unchecked variant for read but not for peek.
This resolves that by making a breaking change to the
Readable interface.
* fix doctests too
Feature Request
Right now, signals have two options for reading:
read()
andpeek()
. Both of these will panic if the signal's value has been dropped, but this can be prevented withtry_read()
. There is currently no way to do the same forpeek()
.Implement Suggestion
Add a way to peek signals without panicking if the underlying value has been dropped. Presumably this would live in the
Readable
trait with the other methods.The text was updated successfully, but these errors were encountered: