From 1fb13d3e9379b0f54583865142b0c318f513f747 Mon Sep 17 00:00:00 2001 From: Michele Caini Date: Mon, 27 Feb 2023 15:32:06 +0100 Subject: [PATCH] doc: minor changes --- src/entt/entity/registry.hpp | 20 +------------------- 1 file changed, 1 insertion(+), 19 deletions(-) diff --git a/src/entt/entity/registry.hpp b/src/entt/entity/registry.hpp index 47e0b8624..7aed94683 100644 --- a/src/entt/entity/registry.hpp +++ b/src/entt/entity/registry.hpp @@ -1221,12 +1221,6 @@ public: /** * @brief Returns a view for the given components. - * - * Views are created on the fly and share with the registry its internal - * data structures. Feel free to discard them after the use.
- * Creating and destroying a view is an incredibly cheap operation. As a - * rule of thumb, storing a view should never be an option. - * * @tparam Type Type of component used to construct the view. * @tparam Other Other types of components used to construct the view. * @tparam Exclude Types of components used to filter the view. @@ -1248,19 +1242,7 @@ public: /** * @brief Returns a group for the given components. * - * Groups are created on the fly and share with the registry its internal - * data structures. Feel free to discard them after the use.
- * Creating and destroying a group is an incredibly cheap operation. As a - * rule of thumb, storing a group should never be an option. - * - * Groups support exclusion lists and can own types of components. The more - * types are owned by a group, the faster it is to iterate entities and - * components.
- * However, groups also affect some features of the registry such as the - * creation and destruction of components. - * - * @note - * Pools of components that are owned by a group cannot be sorted anymore. + * Group owned component pools can no longer be sorted.
* The group takes the ownership of the pools and arrange components so as * to iterate them as fast as possible. *