How would one create a registry with the sigh mixin disabled?

[Avelina9X]

I'm utilising multiple registries, and I'd like the sigh mixin to be enabled for the main registry but must be disabled for all other registries to prevent auto-binding.

How exactly would one achieve this? I think theoretically I could create an alternate entity type and then specialise the storage_type struct for this entity type without the sigh mixin, however this would mess with my entire API because the assumption is that all registries are of type entt::registry and all entities are of type entt::entity.

Manual connection of listeners over auto-binding is also an option, but this will be a massive pain as we do don't know which components exist nor which components need listeners at the time of the main registry's creation, so we'd have to manually create a type list of such components and then update this list whenever new components which need listeners are added to the codebase.

[skypjack]

I think theoretically I could create an alternate entity type and then specialise the storage_type struct for this entity type without the sigh mixin

This is your only option. The storage definition comes from storage_type, which is specialized on the component and entity types.
The registry only understands entity types, while it uses storage_type to lazy initialize storage classes when the time comes (and the component type is known for a moment).
No way you can have two registry types with the same entity and different storage types. I'm sorry.

[Avelina9X]

Alright, thank you for the answer!

I'll have to reexamine my API and see if it makes more sense to keep autobinding and use custom storage, or switch to some sort of RTTI based signal binding instead.

It's times like this that I wish C++ had compile time reflection that doesn't depend on explicit instantiations...