posts: polymorphic-flyweight: fix lint issues
This commit is contained in:
parent
5b5a9bbd5d
commit
eb5bb5e217
|
@ -41,7 +41,7 @@ I also want to use RAII effectively, to avoid the headache of juggling
|
||||||
lifetimes.
|
lifetimes.
|
||||||
|
|
||||||
To this effect, I need to store some `std::unique_ptr<TextureInterface>` inside
|
To this effect, I need to store some `std::unique_ptr<TextureInterface>` 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`.
|
values behind the `TextureInterface`.
|
||||||
|
|
||||||
[std::type_info](https://en.cppreference.com/w/cpp/types/type_info) comes to
|
[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
|
chunks of types, and then sort the values inside the chunks by calling an
|
||||||
ordering method on my polymorphic objects.
|
ordering method on my polymorphic objects.
|
||||||
|
|
||||||
|
|
||||||
## Implementation
|
## Implementation
|
||||||
|
|
||||||
The abstract class looked like this:
|
The abstract class looked like this:
|
||||||
|
|
Loading…
Reference in a new issue