Jacques Lucke
eedcf1876a
This moves all multi-function related code in the `functions` module into a new `multi_function` namespace. This is similar to how there is a `lazy_function` namespace. The main benefit of this is that many types names that were prefixed with `MF` (for "multi function") can be simplified. There is also a common shorthand for the `multi_function` namespace: `mf`. This is also similar to lazy-functions where the shortened namespace is called `lf`.
34 lines
683 B
C++
34 lines
683 B
C++
/* SPDX-License-Identifier: GPL-2.0-or-later */
|
|
|
|
#pragma once
|
|
|
|
/** \file
|
|
* \ingroup fn
|
|
*
|
|
* An #Context is passed along with every call to a multi-function. Right now it does nothing,
|
|
* but it can be used for the following purposes:
|
|
* - Pass debug information up and down the function call stack.
|
|
* - Pass reusable memory buffers to sub-functions to increase performance.
|
|
* - Pass cached data to called functions.
|
|
*/
|
|
|
|
#include "BLI_utildefines.h"
|
|
|
|
#include "BLI_map.hh"
|
|
|
|
namespace blender::fn::multi_function {
|
|
|
|
class Context;
|
|
|
|
class ContextBuilder {
|
|
};
|
|
|
|
class Context {
|
|
public:
|
|
Context(ContextBuilder & /*builder*/)
|
|
{
|
|
}
|
|
};
|
|
|
|
} // namespace blender::fn::multi_function
|