libfuture-perl 0.50-1 source package in Ubuntu

Changelog

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

  * Import upstream version 0.50.
  * Update test dependencies.
  * Update years of upstream and packaging copyright.
  * Declare compliance with Debian Policy 4.6.2.
  * Add libfuture-xs-perl to Recommends and Build-Depends-Indep.
  * Make test dependency on libtest2-suite-perl versioned.

 -- gregor herrmann <email address hidden>  Sun, 11 Jun 2023 17:13: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
Oracular release universe misc
Noble release universe misc
Mantic release universe misc

Builds

Mantic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libfuture-perl_0.50-1.dsc 2.4 KiB 71ec337285db5ef422000826f9be1e24f088014a5591b473bcbc609ded58f1b1
libfuture-perl_0.50.orig.tar.gz 99.4 KiB c035e3d9e69a3af144b33ac834dee9e65ad360f2a51db9f158dc342ecddd5f44
libfuture-perl_0.50-1.debian.tar.xz 3.8 KiB 64cb81ffd650a42dd79a891d8ad47eb9164f229c32149397c984b3f45effc35d

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.