Michele Caini
Michele Caini
Actually, I think the current implementation doesn't work as expected. I'm testing it on a 32 system and it triggers a warning that wasn't there before.
Can you target branch `wip`, please? Thanks (also for the PR, really appreciated!!).
At the moment, you can only iterate all entities (`registry::each`) and `if` them explicitly. However, what you're asking for is on the roadmap. This is the final interface fyi: ```cpp...
If you create a base component and exlude it, it doesn't mean that all derived classes are also excluded as a consequence. I guess this answers your question.
Oh, sorry, didn't get it. Then I would go with the `BaseComponent` since it will be easier to update later on (just replace `BaseComponent` with `void` and you're done).
The answer is exactly the same: the plan is to put all entities in their own storage. Then `on_construct` is the answer.
Do you have a repro for the issue with C++20 ranges? It would be great if we could reproduce it easily on godbolt or at least one of the major...
Uhm, that's interesting. I can't see the reason though. Any idea?
Not sure I want to do _something_ then, I'm of the party that discourages importing namespaces as a whole. 🙂 Any good reason for which we should try to address...
> The constructor should have never been implicit in the first place, especially because it accepts all inputs. I'm not 100% sold on this though. `std::any` also has a catch-all...