Chaining and auto bundler generalization

[jrmadsen]

Overview

• Bundlers now support chaining together function calls for most functions
• New function for checking whether component properties/metadata has been specialized
  • component::properties<T>::specialized()
  • component::metadata<T>::specialized()
• improvements to component::data_tracker and data::handler
• utility::transient_function: alternative to std::function which never allocates on the heap and takes less time to compile
  • this should only be used in synchronous calls and cannot be referenced
  • future updates will use this more often for initialization functions
• the "auto" bundlers now contain significantly less code thanks to a new auto_base_bundler static polymorphic base class
  • SIGNIFICANTLY reduced the amount of auto-bundler code
  • A similar technique will be applied to non-auto component bundlers but this is more complicated for various reasons
• Minor fixes timemory.analysis
• Added operator() for various operations
• Added trait::default_runtime_enabled trait. This can be specialized to have a component default to being disabled at runtime
• bundlers can now execute functions

New Features

Bundler Chaining

The vast majority of bundler member functions return references to itself, thus, you can now chain member function calls like .start().store(i).audit(i). Additionally, there is a execute(...) member function which will execute some function and store the result (w/o copying) so you can return the result after the chain completes. Here is an example:

using bundler_t = component_tuple<wall_clock, peak_rss, data_tracker_integer>;
int foo(int i)
{
    bundler_t _obj{ "foo" };
    _obj.start().store(std::plus<int>{}, i)

    return ...;
}

int bar(int i)
{
    // returns the result of foo(i)
    return bundle_t{ "bar" }.start().audit(i).execute(foo, i).stop().return_result();
}

Transient Function

struct foo
{
    using transient_type = utility::transient_function<void(foo&)>;

    // transient_function replaces std::function usage here
    foo(transient_type _init_func = [](foo&) {})
    {
        _init_func(*this);
    }
};

void bar()
{
    foo _obj{ [](foo& f) { ... } };
}

Bug fixes

• Statistics
  • There was a SFINAE error in math::compute<T>::min(...) and math::compute<T>::max(...) that was causing min/max to not get computed correctly in statistics

[codecov]

Codecov Report

Merging #155 (15c4c24) into develop (5e90eb8) will increase coverage by 0.65%.
The diff coverage is 91.75%.

@@             Coverage Diff             @@
##           develop     #155      +/-   ##
===========================================
+ Coverage    79.36%   80.00%   +0.65%     
===========================================
  Files          235      240       +5     
  Lines        16146    16680     +534     
===========================================
+ Hits         12812    13343     +531     
- Misses        3334     3337       +3     

Impacted Files	Coverage Δ
source/timemory/components/base/declaration.hpp	30.00% <ø> (ø)
source/timemory/components/properties.hpp	66.67% <ø> (ø)
source/timemory/mpl/apply.hpp	94.60% <ø> (ø)
source/timemory/mpl/math.hpp	96.71% <ø> (+0.16%)	⬆️
source/timemory/mpl/type_traits.hpp	100.00% <ø> (ø)
source/timemory/mpl/types.hpp	100.00% <ø> (ø)
source/timemory/operations/types/generic.hpp	80.96% <ø> (ø)
source/timemory/storage/definition.hpp	79.53% <0.00%> (+0.44%)	⬆️
source/timemory/utility/mangler.hpp	100.00% <ø> (ø)
source/timemory/operations/types/node.hpp	80.00% <56.25%> (-8.05%)	⬇️
... and 65 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5e90eb8...15c4c24. Read the comment docs.