-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Pull Schedules::ignored_scheduling_ambiguities into a separate resource and avoid unnecessary allocation
#21929
New issue
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
Open
ItsDoot
wants to merge
2
commits into
bevyengine:main
Choose a base branch
from
ItsDoot:schedule/ambiguity-resource
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+87
−71
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| use core::{ | ||
| fmt::Write as _, | ||
| ops::{Deref, DerefMut}, | ||
| }; | ||
|
|
||
| use alloc::string::{String, ToString}; | ||
| use bevy_platform::collections::HashSet; | ||
|
|
||
| use crate::{ | ||
| component::{ComponentId, Components}, | ||
| resource::Resource, | ||
| }; | ||
|
|
||
| /// List of [`ComponentId`]s to ignore when reporting system order ambiguity conflicts. | ||
| #[derive(Resource, Default)] | ||
| pub struct IgnoredAmbiguities(pub HashSet<ComponentId>); | ||
|
|
||
| impl IgnoredAmbiguities { | ||
| /// Returns a string listing all ignored ambiguity component names. | ||
| /// | ||
| /// May panic or retrieve incorrect names if [`Components`] is not from the | ||
| /// same world. | ||
| pub fn to_string(&self, components: &Components) -> String { | ||
| let mut message = | ||
| "System order ambiguities caused by conflicts on the following types are ignored:\n" | ||
| .to_string(); | ||
| for id in self.iter() { | ||
| writeln!(message, "{}", components.get_name(*id).unwrap()).unwrap(); | ||
| } | ||
| message | ||
| } | ||
| } | ||
|
|
||
| impl Deref for IgnoredAmbiguities { | ||
| type Target = HashSet<ComponentId>; | ||
|
|
||
| fn deref(&self) -> &Self::Target { | ||
| &self.0 | ||
| } | ||
| } | ||
|
|
||
| impl DerefMut for IgnoredAmbiguities { | ||
| fn deref_mut(&mut self) -> &mut Self::Target { | ||
| &mut self.0 | ||
| } | ||
| } | ||
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Each schedule is going to produce it's own ambiguities. Shouldn't this be like
HashMap<ScheduleLabel, IndexSet<ComponentId>>? or maybe a component might be better. Since you can store schedules outside of theSchedulesresource and this would keep them from overwriting if they share a schedule label.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ScheduleGraph::ambiguous_with_allandScheduleGraph::ambiguous_withare the per-Scheduleambiguity stores, this is the global one. I'm just moving the global one outside of theSchedulesresource. I can add a flag toSchedulefor whether it should use the global storage or not?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could also do a two-tier system where each
Schedulealso has their ownHashSet<ComponentId>, and have a flag to also fetch from the global set.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, before and after this PR as-is, all
Schedules have to adhere to the global ambiguity set. So adding an opt-out would be a new thing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The engine itself doesn't iterate the set, and I can't find any examples on GitHub (including
bevy_mod_debugdump) of people iterating the set, so I don't think we need to make it anIndexSet.