forestia/bevy
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

correct "its"

Browse Source
This commit is contained in:
Carter Anderson 2020-05-04 14:18:46 -07:00
parent 4735c68ab4
commit 7560ecf9d8
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
crates/bevy_render/src/render_graph/command.rs
View File

@ -24,7 +24,7 @@ pub enum Command {
#[derive(Default, Clone)] #[derive(Default, Clone)]
pub struct CommandQueue { pub struct CommandQueue {
// TODO: this shouldn't really need a mutex. its just needs to be shared on whatever thread its scheduled on // TODO: this shouldn't really need a mutex. it just needs to be shared on whatever thread it's scheduled on
queue: Arc<Mutex<Vec<Command>>>, queue: Arc<Mutex<Vec<Command>>>,
} }

2
crates/bevy_wgpu/src/wgpu_render_pass.rs
View File

@ -98,7 +98,7 @@ impl<'a> RenderPass for WgpuRenderPass<'a> {
}; };
// don't bind bind groups if they are already set // don't bind bind groups if they are already set
// TODO: these checks come at a performance cost. make sure its worth it! // TODO: these checks come at a performance cost. make sure it's worth it!
if let Some(bound_render_resource_set) = if let Some(bound_render_resource_set) =
self.bound_bind_groups.get(&bind_group.index) self.bound_bind_groups.get(&bind_group.index)
{ {

2
examples/ecs/ecs_guide.rs
View File

@ -339,7 +339,7 @@ fn main() {
.add_system_to_stage("after_round", score_check_system.system()) .add_system_to_stage("after_round", score_check_system.system())
.add_system_to_stage("after_round", game_over_system.system()) .add_system_to_stage("after_round", game_over_system.system())
// score_check_system will run before game_over_system because score_check_system modifies GameState and game_over_system // score_check_system will run before game_over_system because score_check_system modifies GameState and game_over_system
// reads GameState. This works, but its a bit confusing. In practice, it would be clearer to create a new stage that runs // reads GameState. This works, but it's a bit confusing. In practice, it would be clearer to create a new stage that runs
// before "after_round" // before "after_round"
// This call to run() starts the app we just built! // This call to run() starts the app we just built!