We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We can do this by storing registered events in a sorted list of typeids, then assigning channel ids based on index.
The text was updated successfully, but these errors were encountered:
Agree, but shouldn't use TypeId since it's not stable across binaries. Relevant issue in Bevy. But it looks like we can just use type names.
Sorry, something went wrong.
It looks like type_name is also not stable.
Hm... Yes, I missed it. That just what @cart suggested in bevyengine/bevy#32 (comment). Then I'm not sure how to solve it properly.
@cart
No branches or pull requests
We can do this by storing registered events in a sorted list of typeids, then assigning channel ids based on index.
The text was updated successfully, but these errors were encountered: