Description

Build a call stack within separate thread and capture diagnostics.

The actual test operation produces a descending number sequence, and only odd values will be captured into the diagnostic stack-

Public Member Functions
	TestThread ()

Public Member Functions inherited from ThreadJoinable< RES >
lib::Result< RES >	join ()
	put the caller into a blocking wait until this thread has terminated

Public Member Functions inherited from ThreadLifecycle< POL, RES >
	ThreadLifecycle (Launch launcher)
	Primary constructor: Launch the new thread with flexible configuration.

template<class FUN , typename... ARGS>
	ThreadLifecycle (string const &threadID, FUN &&threadFunction, ARGS &&...args)
	Create a new thread to execute the given operation.

template<class SUB , typename... ARGS>
	ThreadLifecycle (RES(SUB::*memFun)(ARGS...), ARGS ...args)
	Special variant to bind a subclass member function as thread operation.

	operator bool () const
	Is this thread »active« and thus tied to OS resources?

Additional Inherited Members
Static Public Member Functions inherited from ThreadLifecycle< POL, RES >
template<class W , class... INVO>
static auto	buildInvocation (W &wrapper, tuple< INVO... > &&invocation)
	Build the invocation tuple, using invokeThreadFunction to delegate to the user-provided functor and arguments.

template<class... INVO>
static auto	buildLauncher (INVO &&...args)
	Build a λ actually to launch the given thread operation later, after the thread-wrapper-object is fully initialised.

Protected Member Functions inherited from ThreadLifecycle< POL, RES >
	~ThreadLifecycle ()

	ThreadLifecycle ()
	derived classes may create a disabled thread

Constructor & Destructor Documentation

TestThread ( )

inline

Here is the call graph for this function:

Inheritance diagram for DiagnosticContext_test::TestThread:

Collaboration diagram for DiagnosticContext_test::TestThread:

The documentation for this struct was generated from the following file: