openKylin libfuture-perl package

libfuture-perl 0.50-ok1 source package in openKylin

libfuture-perl (0.50-ok1) nile; urgency=medium

  * Build for openKylin.

 -- openKylinBot <email address hidden>  Tue, 07 May 2024 09:40:57 +0800

Series	Pocket	Published	Component	Section
Huanghe V3.0	proposed	on 2024-10-15	main	perl
Huanghe V3.0	release	on 2024-10-15	main	perl
Nile V2.0	release	on 2024-06-21	main	perl
Nile V2.0	proposed	on 2024-05-07	main	perl

File	Size	SHA-256 Checksum
libfuture-perl_0.50.orig.tar.gz	99.4 KiB	c035e3d9e69a3af144b33ac834dee9e65ad360f2a51db9f158dc342ecddd5f44
libfuture-perl_0.50-ok1.debian.tar.xz	2.4 KiB	7d21d580ba5dbf83e56333fb8468bc779c53784008cd1ef6c191aac3aab20fac
libfuture-perl_0.50-ok1.dsc	2.0 KiB	8503d67174bd3dba00ebb27a86b4002721ab6b0ce11dbc2507a452f19e3db952

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.