Archetype invariants #5
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Closing for now as its on the backburner. Ping me if you want me to prioritize this work, or give advice on your own RFC for this. |
Weibye
pushed a commit
to Weibye/rfcs
that referenced
this pull request
Apr 24, 2022
Remove angle as a component
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RENDERED
Archetype invariants are global rules about which archetypes can exist in a Bevy app's ECS.
By defining which components must or cannot coexist, we can enforce domain-specific rules to ensure correctness.
Once these rules are encoded into our ECS, we can leverage them to improve performance in a large variety of ways.
First discussed in bevyengine/bevy#1481.