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

Update increment_change_tick to return a strongly-typed Tick (#8295)

Browse Source 
# Objective

While migrating the engine to use the `Tick` type in #7905, I forgot to
update `UnsafeWorldCell::increment_change_tick`.

## Solution

Update the function.

---

## Changelog

- The function `UnsafeWorldCell::increment_change_tick` is now
strongly-typed, returning a value of type `Tick` instead of a raw `u32`.

## Migration Guide

The function `UnsafeWorldCell::increment_change_tick` is now
strongly-typed, returning a value of type `Tick` instead of a raw `u32`.
This commit is contained in:
JoJoJet 2023-04-03 13:42:27 -04:00 committed by GitHub
parent 09f1bd0be7
commit 086db6d22f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
crates/bevy_ecs/src/world/unsafe_world_cell.rs
View File

@ -202,12 +202,10 @@ impl<'w> UnsafeWorldCell<'w> {
}
#[inline]
pub fn increment_change_tick(self) -> u32 {
pub fn increment_change_tick(self) -> Tick {
// SAFETY:
// - we only access world metadata
unsafe { self.world_metadata() }
.change_tick
.fetch_add(1, Ordering::AcqRel)
unsafe { self.world_metadata() }.increment_change_tick()
}
/// Shorthand helper function for getting the [`ArchetypeComponentId`] for a resource.