Bug#1068927: ITP: rust-event-listener-strategy -- block or poll on event_listener easily
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard <dr@jones.dk>
X-Debbugs-Cc: debian-devel@lists.debian.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
* Package name : rust-event-listener-strategy
Version : 0.5.1
Upstream Contact: John Nunley <dev@notgull.net>
* URL : https://github.com/smol-rs/event-listener-strategy
* License : Apache-2.0 or Expat
Programming Lang: Rust
Description : block or poll on event_listener easily
event-listener-strategy provides a strategy
for using the event-listener crate
in both blocking and non-blocking contexts.
.
One of the stand-out features of the event-listener crate
is the ability to use it in both asynchronous and synchronous contexts.
However, sometimes using it like this
causes a lot of boilerplate to be duplicated.
This crate aims to reduce that boilerplate
by providing an EventListenerFuture trait
that implements both blocking and non-blocking functionality.
This package is needed for newer releases of src:rust-async-lock and
src:rust-async-channel.
It will be maintained in the collaborative Debian section of Salsa, at
https://salsa.debian.org/debian/rust-event-listener-strategy
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYaklcACgkQLHwxRsGg
ASHWLhAAoN2U3vUvMe6vng6U0BCHoImeJor7wGb0RsR8SagWtONeDyubBoK/kNgx
lWhvgwcLcgc4bTKPdqqfH44svsQ9qMAQFdYp9QZZXXuUJCKwPjlbrgwcEpUu0gy1
H3mVsZOzwWH2ldnlE6F71L+uQSJriaCyN5HbFXfkXIo25WELcE0trGJletqHuiVM
cONmMXGSFNjPc6DFNOfIAUrfyIt9qp1urCu4nzLWsvxBV3CgrUyPBZLlcezOa9wd
NfVv2A2FVwxDYqst5hwckmemgjr/82Y5jn8Wd644vhlxIHN7cNFq8awQ1wY3Bz8/
C9VuVyz7P0NCotqM0oWosYk+hZyDEGkiapFiGPQlQSbPTSbBdPRLoMd25W6ABSxk
wnW9mBPRhebNl30ZODCePM1PRlM8DhVygeIFkXs3kBScLSRjAMtHh3c4EWw3pcls
7e819qb/mHce4xcrHxeybCl5DB3k6pDpn6+0gHYemrbpAsCcr9aWLoRxTMbh9Uin
5vYugGlaROdD13Ojkinbm+HXmwEEWqTXu/y2M+dzNJNIRS45XsOSAq6nHZKot3jg
/LlwCresEdWv7UY8PO4Z21EoXUSrStA8pIqqJyzKx+hXvf/l1vIvV8iYLWDgGGmU
ht7rS5GLaoXx2HI0o1hFDeMFU51F0D5Vy6unvbKulJNzv7fLVyA=
=Cau5
-----END PGP SIGNATURE-----
Reply to: