Ravenports generated: 22 May 2022 14:00
[ravenports.git] / bucket_B9 / R-future.apply
1 # Buildsheet autogenerated by ravenadm tool -- Do not edit.
2
3 NAMEBASE=               R-future.apply
4 VERSION=                1.9.0
5 KEYWORDS=               cran
6 VARIANTS=               standard
7 SDESC[standard]=        Apply Function in Parallel using Futures
8 HOMEPAGE=               https://future.apply.futureverse.org
9 CONTACT=                CRAN_Automaton[cran@ironwolf.systems]
10
11 DOWNLOAD_GROUPS=        main
12 SITES[main]=            CRAN/src/contrib
13 DISTFILE[1]=            future.apply_1.9.0.tar.gz:main
14 DIST_SUBDIR=            CRAN
15 DF_INDEX=               1
16 SPKGS[standard]=        single
17
18 OPTIONS_AVAILABLE=      none
19 OPTIONS_STANDARD=       none
20
21 BUILDRUN_DEPENDS=       R-future:single:standard
22                         R-globals:single:standard
23
24 USES=                   cran gmake
25
26 DISTNAME=               future.apply
27
28 GENERATED=              yes
29
30 INSTALL_REQ_TOOLCHAIN=  yes
31
32 [FILE:525:descriptions/desc.single]
33 future.apply: Apply Function to Elements in Parallel using Futures
34
35 Implementations of apply(), by(), eapply(), lapply(), Map(), .mapply(),
36 mapply(), replicate(), sapply(), tapply(), and vapply() that can be
37 resolved using any future-supported backend, e.g. parallel on the local
38 machine or distributed on a compute cluster. These future_*apply()
39 functions come with the same pros and cons as the corresponding base-R
40 *apply() functions but with the additional feature of being able to be
41 processed via the future framework.
42
43
44 [FILE:109:distinfo]
45 6166c1c5ce30b9745059c3d30c8110f7c1d51871e58aa414f195cb1f91c467f5        64200 CRAN/future.apply_1.9.0.tar.gz
46