This is the source code repository of the Software Technology Lab (STLab).
ASL libraries will be migrated here in the stlab
namespace, new libraries will be created here.
This library provides futures and channels, high level abstractions for implementing algorithms that eases the use of multiple CPU cores while minimizing contention. This library solves several problems of the C++11 and C++17 TS futures.
The complete documentation is available on the STLab home page.
Release changelogs are listed in CHANGES.md.
- All OS that have a C++14 compliant compiler
- C++14 Compiler -- Visual Studio 2017 (>= 15.9.0), Visual Studio 2019 -- gcc (>= 7) -- clang (>= 6)
- boost.optional and boost.variant if the compiler's library does not provide them
- boost.test only for the unit tests
First, you will need the following tools:
conan
and cmake
are available on the Mac via Homebrew. cmake
is available on Windows via scoop
.
Once they're set up, run either setup_xcode.sh
or setup_msvc.bat
for the platform of your choice. It will setup all necessary library dependencies and create the platform-specific project file in the ./build/
directory.
Microsoft Windows Platform Build Notes:
- If you are using
conan
for the first time, add--build missing
to conan command call insetup_msvc.bat
script - Use administrator command prompt if you get issues in manifest creation during
setup_msvc.bat
run (ex:mt : general error c101008d
)
- Currently we are redesigning the interface of the
future
class. We will make the associated executor of a task more explicit by removing the implicit "inheritance" of the executors from the previous future. So a continuation will not get automatically the same executor from its predecessor. If non is provided, then it will be automatically be executed via theimmediate_executor
. - As well we will remove all
.then()
and.recover()
functions from thefuture
interface. Only theoperator|()
andoperator^()
will remain. So the pipe notation, as it is comming with C++20 ranges, will become the only choice. Obviously this will be a breaking change. - In parallel we think about changing the then former
recover()
function signature, see issue #263.