|
|
@@ -7,7 +7,6 @@
|
|
|
|
|
|
* [Introduction](#introduction)
|
|
|
* [Definitions](#definitions)
|
|
|
- * [ENTT_STANDALONE](#entt_standalone)
|
|
|
* [ENTT_NOEXCEPT](#entt_noexcept)
|
|
|
* [ENTT_HS_SUFFIX and ENTT_HWS_SUFFIX](#entt_hs_suffix_and_entt_hws_suffix)
|
|
|
* [ENTT_USE_ATOMIC](#entt_use_atomic)
|
|
|
@@ -38,14 +37,6 @@ Each parameter can result in internal library definitions. It's not recommended
|
|
|
to try to also modify these definitions, since there is no guarantee that they
|
|
|
will remain stable over time unlike the options below.
|
|
|
|
|
|
-## ENTT_STANDALONE
|
|
|
-
|
|
|
-`EnTT` is designed in such a way that it works (almost) everywhere out of the
|
|
|
-box. However, this is the result of many refinements over time and a compromise
|
|
|
-regarding some optimizations.<br/>
|
|
|
-It's worth noting that users can get a small performance boost by passing this
|
|
|
-definition to the compiler when the library is used in a standalone application.
|
|
|
-
|
|
|
## ENTT_NOEXCEPT
|
|
|
|
|
|
The purpose of this parameter is to suppress the use of `noexcept` by this
|
Michele Caini