From eb5bb5e217929ef25ecaf595a7e66ade5107cc8c Mon Sep 17 00:00:00 2001 From: Bruno BELANYI Date: Thu, 27 Aug 2020 17:32:57 +0200 Subject: [PATCH] posts: polymorphic-flyweight: fix lint issues --- content/posts/polymorphic-flyweight-cpp.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/posts/polymorphic-flyweight-cpp.md b/content/posts/polymorphic-flyweight-cpp.md index 5513a60..ce2b442 100644 --- a/content/posts/polymorphic-flyweight-cpp.md +++ b/content/posts/polymorphic-flyweight-cpp.md @@ -41,7 +41,7 @@ I also want to use RAII effectively, to avoid the headache of juggling lifetimes. To this effect, I need to store some `std::unique_ptr` inside -my set. However, to do so I need to come up with a way to totally order my +my set. However, to do so I need to come up with a way to totally order my values behind the `TextureInterface`. [std::type_info](https://en.cppreference.com/w/cpp/types/type_info) comes to @@ -52,7 +52,6 @@ I could order my textures by their `std::type_index` to order them first by chunks of types, and then sort the values inside the chunks by calling an ordering method on my polymorphic objects. - ## Implementation The abstract class looked like this: