<?xml version="1.0" encoding="UTF-8"?>
<oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:title>Apply Function to Elements in Parallel using Futures</dc:title>
  <dc:title>R package future.apply version 1.20.2</dc:title>
  <dc:subject>CRAN Task View: HighPerformanceComputing (https://CRAN.R-project.org/view=HighPerformanceComputing)</dc:subject>
  <dc:description>Implementations of apply(), by(), eapply(), lapply(), Map(), .mapply(), mapply(), replicate(), sapply(), tapply(), and vapply() that can be resolved using any future-supported backend, e.g. parallel on the local machine or distributed on a compute cluster. These future_*apply() functions come with the same pros and cons as the corresponding base-R *apply() functions but with the additional feature of being able to be processed via the future framework &lt;doi:10.32614/RJ-2021-048&gt;.</dc:description>
  <dc:type>Software</dc:type>
  <dc:relation>Depends: R (&gt;= 3.2.0), future (&gt;= 1.49.0)</dc:relation>
  <dc:relation>Imports: globals, parallel, utils</dc:relation>
  <dc:relation>Suggests: datasets, stats, tools, listenv, R.rsp, markdown</dc:relation>
  <dc:creator>Henrik Bengtsson &lt;henrikb@braju.com&gt;</dc:creator>
  <dc:publisher>Comprehensive R Archive Network (CRAN)</dc:publisher>
  <dc:contributor>Henrik Bengtsson [aut, cre, cph] (ORCID:
    &lt;https://orcid.org/0000-0002-7579-5165&gt;),
  R Core Team [cph, ctb]</dc:contributor>
  <dc:rights>GPL (&gt;= 2)</dc:rights>
  <dc:date>2026-02-20</dc:date>
  <dc:format>application/tgz</dc:format>
  <dc:identifier>https://CRAN.R-project.org/package=future.apply</dc:identifier>
  <dc:identifier>doi:10.32614/CRAN.package.future.apply</dc:identifier>
  <dc:language>en-US</dc:language>
</oai_dc:dc>
