libfuture-perl 0.45-1 source package in Ubuntu

Changelog

libfuture-perl (0.45-1) unstable; urgency=medium

  * Import upstream version 0.45.
  * Add a note about API changes to debian/NEWS.
  * Add additional test dependency.

 -- gregor herrmann <email address hidden>  Sat, 25 Apr 2020 17:07:20 +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 Pocket Published Component Section
Groovy release main misc

Builds

Groovy: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libfuture-perl_0.45-1.dsc 2.4 KiB ac877f164b59bf47f28305a259e9722ab41b09c6e00668bc3ff80bb3f6806404
libfuture-perl_0.45.orig.tar.gz 93.5 KiB ce8cab6bb940434ffbf2465771bf6ed55df36ddca5bebc1024e7d4d07802a6c0
libfuture-perl_0.45-1.debian.tar.xz 3.5 KiB c70486b3a630a52ff955c81333c84b48d0e8411070128eff9dad86d861e45090

Available diffs

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.