遵循以下最佳实践的项目将能够自愿的自我认证,并显示他们已经实现了核心基础设施计划(OpenSSF)徽章。 显示详细资料
[](https://www.bestpractices.dev/projects/1040)
<a href="https://www.bestpractices.dev/projects/1040"><img src="https://www.bestpractices.dev/projects/1040/badge"></a>
Fruit is a dependency injection framework for C++, loosely inspired by the Guice framework for Java. It uses C++ metaprogramming together with some new C++11 features to detect most injection problems at compile-time. It allows to split the implementation code in "components" (aka modules) that can be assembled to form other components. From a component with no requirements it's then possible to create an injector, that provides an instance of the interfaces exposed by the component.
See the wiki for more information, including installation instructions, tutorials and reference documentation.
Repository on GitHub, which uses git. git is distributed.
When Fruit is built using CMake, ctest can be used to run the tests. When Fruit is built using Bazel, Bazel can be used to run the tests.
警告:需要URL,但找不到URL。
Fruit is set up for continuous integration using Travis CI (for Linux and OS X) and Appveyor (for Windows).
Found all required security hardening headers.
Fruit uses GCC and clang's dynamic analyzers (ASan, UBSan), they run for each git push.
There are many debug-only assertions that can be enabled using the FRUIT_DEBUG and FRUIT_EXTRA_DEBUG macros. These assertions are checked when running CI tests in debug mode (so they're checked for every commit).
后退