Assets 2

changelog

- Remove a bug that caused infinite recursion on Visual Studio when trying to
   compose a future with multiple tasks.
- Improve the API that assembles tasks and and their continuations before 
  passing them on to run API.

@mhogomchungu mhogomchungu released this Apr 27, 2018 · 4 commits to master since this release

Assets 4
changelog:
-- Add ability to set all options in the Task::process:result 
class through through its constructor

@mhogomchungu mhogomchungu released this Jan 30, 2018 · 9 commits to master since this release

Assets 4
Changelog:

- Make the library installable. The preferred way to use the library is to 
  include the header file with the rest of the project that has this library 
  as a dependency.

- Some distributions do not like bundled dependencies and now they 
  can easily package it to make it available in their repositories. The argument 
  to pass to cmake to make an installable package is:
  "-DMCHUNGU_TASK_INSTALL=true"

@mhogomchungu mhogomchungu released this Jan 20, 2018 · 18 commits to master since this release

Assets 4
The returned type of a task is no longer required to be specified since it 
can be deduced automatically.

Given a function prototype of:

int woof() ;

Previously, it was required to do something like:

Task::future<int>& foo = Task::run<int>( woof ) ;

Now, the above can simply be written as:

Task::future<int>& foo = Task::run( woof ) ; 

@mhogomchungu mhogomchungu released this Dec 28, 2015 · 77 commits to master since this release

Assets 4

changelog:

Add API that takes a lambda that requires arguments.

Documentation for the new API is below:


  • Example use cases on how to use lambda that requires an argument
    * ******************************************************************
/*
 * declaring "meaw" with an auto keyword will not be sufficient here
 * and the full std::function<blablabla> is required.
 *
 * For the same reason,just plugging in a lambda that requires arguments
 * into Task::run() will not be sufficent and the plugged in lambda must
 * be casted to std::function<blablabla> for it to compile.
 *
 * Why the above restriction? No idea but i suspect it has to do with
 * variadic template type deduction failing to see something.
 */

std::function< int( int ) > meaw = []( int x ){

    return x + 1 ;
} ;

Task::run( meaw,6 ).then( []( int r ){

    qDebug() << r ;
} ) ;

alternatively,

r = Task::await( meaw,6 ) ;

@mhogomchungu mhogomchungu released this Oct 6, 2014 · 100 commits to master since this release

Assets 4

changelog:

change API and substitute "future_1" with "future

@mhogomchungu mhogomchungu released this Aug 15, 2014 · 103 commits to master since this release

Assets 3

version 1.0.0 had only Task::run().then() API

This version adds Task::await() API

Jul 17, 2014
tagging version 1.0.0