Deprecated: $wgMWOAuthSharedUserIDs=false is deprecated, set $wgMWOAuthSharedUserIDs=true, $wgMWOAuthSharedUserSource='local' instead [Called from MediaWiki\HookContainer\HookContainer::run in /var/www/html/w/includes/HookContainer/HookContainer.php at line 135] in /var/www/html/w/includes/Debug/MWDebug.php on line 372
future.apply - MaRDI portal

future.apply (Q45068)

From MaRDI portal
Apply Function to Elements in Parallel using Futures
Language Label Description Also known as
English
future.apply
Apply Function to Elements in Parallel using Futures

    Statements

    0 references
    1.10.0
    5 November 2022
    0 references
    1.11.0
    21 May 2023
    0 references
    0.1.0
    15 January 2018
    0 references
    0.2.0
    1 May 2018
    0 references
    1.0.0
    20 June 2018
    0 references
    1.0.1
    27 August 2018
    0 references
    1.1.0
    17 January 2019
    0 references
    1.2.0
    7 March 2019
    0 references
    1.3.0
    18 June 2019
    0 references
    1.4.0
    7 January 2020
    0 references
    1.5.0
    17 April 2020
    0 references
    1.6.0
    1 July 2020
    0 references
    1.7.0
    4 January 2021
    0 references
    1.8.1
    10 August 2021
    0 references
    1.9.0
    26 April 2022
    0 references
    1.9.1
    7 September 2022
    0 references
    1.11.1
    21 December 2023
    0 references
    0 references
    21 December 2023
    0 references
    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.
    0 references
    0 references
    0 references
    0 references
    0 references

    Identifiers

    0 references
    0 references