libfuture-perl 0.49-1 source package in Ubuntu
Changelog
libfuture-perl (0.49-1) unstable; urgency=medium * Import upstream version 0.49. * Declare compliance with Debian Policy 4.6.1. -- gregor herrmann <email address hidden> Sun, 30 Oct 2022 02:31:09 +0200
Upload details
- Uploaded by:
- Debian Perl Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Lunar | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| libfuture-perl_0.49-1.dsc | 2.4 KiB | 1b234aeeb87afa3a7299031796687a052a77525af65c9d7afaf699a8765164ae |
| libfuture-perl_0.49.orig.tar.gz | 99.1 KiB | 49ae7de65a864082b129c1091be0edf6690b9989f9eb1bc1ca1c0553e4e868ce |
| libfuture-perl_0.49-1.debian.tar.xz | 3.8 KiB | 18d12c75c7748f71535f67903d1a2259e38a40f22eadd2bdef9564d1c1f40ee3 |
Available diffs
- diff from 0.48-1 to 0.49-1 (34.3 KiB)
No changes file available.
Binary packages built by this source
- libfuture-perl: module for operations awaiting completion
A Future object represents an operation that is currently in progress, or
has recently completed. It can be used in a variety of ways to manage the
flow of control, and data, through an asynchronous program.
.
Some futures represent a single operation and are explicitly marked as ready
by calling the done or fail methods. These are called "leaf" futures here,
and are returned by the new constructor.
.
Other futures represent a collection sub-tasks, and are implicitly marked as
ready depending on the readiness of their component futures as required.
These are called "dependent" futures here, and are returned by the various
wait_* and need_* constructors.
.
It is intended that library functions that perform asynchronous operations
would use Future objects to represent outstanding operations, and allow their
calling programs to control or wait for these operations to complete. The
implementation and the user of such an interface would typically make use of
different methods on the class. The methods below are documented in two
sections; those of interest to each side of the interface.
